2.1 |
Approval of the agenda |
|
R2-2204400 |
Agenda for RAN2#118-e |
Chairman |
2.2 |
Approval of the report of the previous meeting |
|
R2-2204401 |
RAN2#117-e Meeting Report |
MCC |
R2-2204402 |
RAN2 Rel-17 ASN.1 AdHoc Meeting Report |
MCC |
2.4 |
Others |
|
R2-2204403 |
RAN2 Handbook 05-22 |
MCC |
R2-2204404 |
Check-in procedure in 3GPP meetings |
MCC |
R2-2206721 |
Correction on MRO for SN Change Failure |
R3 (Lenovo) |
R2-2206722 |
Inter-system direct data forwarding between source SgNB and target gNB |
R3 (Ericsson) |
R2-2206723 |
Inter-system direct data forwarding between source SgNB and target gNB |
R3 (Ericsson) |
R2-2206724 |
Correction on R17 SON MDT for TS36.300 |
R3 (ZTE,China Unicom, China Telecom) |
R2-2206725 |
IAB Rel-17 Corrections |
R3 (Ericsson) |
R2-2206726 |
Correction on NR MBS |
R3 (Huawei, CBN, China Unicom, Nokia, Nokia Shanghai Bell) |
R2-2206727 |
Correction of MBS data forwarding |
R3 (Nokia, Nokia Shanghai Bell, Huawei) |
R2-2206728 |
Correction on RA-SDT overall procedures |
R3 (CATT, ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Google, China Telecom, LG Electronics, NEC, Intel Corporation) |
R2-2206729 |
Stage 2 corrections for NR Positioning Enhancements |
R3 (Nokia, Nokia Shanghai Bell) |
R2-2206730 |
Corrections for NR NTN |
R3 (Nokia, Nokia Shanghai Bell, CATT, Thales) |
R2-2206731 |
Stage 2 Correction on NB-IoT and eMTC Support for NTN |
R3 (ZTE) |
R2-2206732 |
Stage-2 aspects for CPAC |
R3 (Ericsson, Qualcomm Incorporated, Intel Corporation, ZTE, Lenovo, CATT) |
R2-2206733 |
Corrections to UE History Information in MR-DC |
R3 (Huawei, CMCC, Qualcomm, Deutsche Telekom, Ericsson) |
R2-2206734 |
RACH optimisation in EN-DC secondary cell |
R3 (Nokia, Nokia Shanghai Bell,CATT, Ericsson) |
R2-2206735 |
Correction on R17 SON MDT for 38.300 |
R3 (ZTE) |
R2-2206736 |
Correction of the "last used cell" in UE Context Release Complete |
R3 (Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CATT, Samsung, Qualcomm Incorporated) |
R2-2206737 |
Clarifications for NB-IOT UE |
R3 (Nokia, Nokia Shanghai Bell, Huawei) |
R2-2206738 |
QoE Rel-17 Corrections |
R3 (Ericsson) |
R2-2206739 |
Correction on NR MBS mobility for 38300 |
R3 (ZTE) |
R2-2206740 |
TS 38.300 corrections for CCO |
R3 (Ericsson, Deutsche Telekom, Qualcomm Incorporated) |
R2-2206772 |
Correction on R17 SON MDT for TS36.300 |
R3 (ZTE,China Unicom, China Telecom) |
R2-2206817 |
Stage 2 corrections for NR Positioning Enhancements |
R3 (Nokia, Nokia Shanghai Bell) |
R2-2206830 |
Stage-2 aspects for CPAC |
R3 (Ericsson, Qualcomm Incorporated, Intel Corporation, ZTE, Lenovo, CATT) |
R2-2206854 |
Correction on R17 SON MDT for TS36.300 |
R3 (ZTE,China Unicom, China Telecom) |
R2-2206855 |
RACH optimisation in EN-DC secondary cell |
R3 (Nokia, Nokia Shanghai Bell,CATT, Ericsson) |
R2-2206856 |
Stage-2 aspects for CPAC |
Ericsson, Qualcomm Incorporated, Intel Corporation, ZTE, Lenovo, CATT |
R2-2206875 |
Correction of MBS data forwarding |
R3 (Nokia, Nokia Shanghai Bell, Huawei) |
3 |
Incoming liaisons |
|
R2-2204417 |
LS response to 3GPP RAN on Location Services for Drones (LI(21)P59034r1; contact: ETSI TC LI) |
ETSI TC LI |
R2-2204438 |
LS on RAN feedback for low latency (S2-2201767; contact: Huawei) |
SA2 |
R2-2204439 |
LS on QoS support with PDU Set granularity (S2-2201803; contact: Intel) |
SA2 |
R2-2204512 |
LS on presentation of EUWENA and involvement in 3GPP on Non Public Network (contact: Novamint) |
EUWENA |
R2-2204514 |
LS response to ETSI TC LI on Location Services for Drones (RP-220954; contact: Ericsson) |
RAN |
R2-2204515 |
UE capabilities for MBS (S2-2203020; contact: Qualcomm) |
SA2 |
R2-2204523 |
LS on UE Power Saving for XR and Media Services (S2-2203418; contact: Nokia) |
SA2 |
R2-2204530 |
LS on Rel-18 WI related to vehicular distributed antenna systems (S-220026; contact: LGE) |
S4SEM |
R2-2204531 |
Reply LS on UE capabilities for NR QoE (S4-220534; contact: Ericsson) |
SA4 |
R2-2205018 |
Proposed response to SA2 LS R2-2203930 on low latency |
Nokia, Nokia Shanghai Bell |
R2-2205502 |
Discussion on RAN feedback for low latency |
Ericsson |
R2-2205998 |
Discussion of SA2 LS on UE Power Saving for XR and Media Services |
Ericsson |
R2-2206337 |
LS Reply on QoS support with PDU Set granularity (S4-220505; contact: Qualcomm) |
SA4 |
R2-2206554 |
LS on draft TR 38.835 skeleton (R1-2205443; contact: Nokia) |
RAN1 |
R2-2206770 |
LS On FS_REDCAP_Ph2 option feasibility (S2-2204989; contact: Ericsson) |
SA2 |
R2-2206807 |
Reply LS on UE Power Saving for XR and Media Services (R1-2205531; contact: Qualcomm) |
RAN1 |
4.2 |
eMTC corrections Rel-16 and earlier |
|
R2-2205877 |
Correction on calculating number of TBs for multi-TB scheduling |
Oy LM Ericsson AB |
R2-2205879 |
Correction on calculating number of TBs for multi-TB scheduling |
Oy LM Ericsson AB |
R2-2206321 |
Report of [AT118-e][401][eMTC R16] Number of TBs for multi-TB scheduling (Ericsson) |
Ericsson |
R2-2206322 |
Correction on calculating number of TBs for multi-TB scheduling |
Oy LM Ericsson AB |
R2-2206323 |
Correction on calculating number of TBs for multi-TB scheduling |
Oy LM Ericsson AB |
4.5 |
Other LTE corrections Rel-16 and earlier |
|
R2-2205199 |
Minor changes collected by Rapporteur |
Samsung |
R2-2205200 |
Clarifications on CQI-ReportPeriodicScell |
Samsung |
R2-2205201 |
Correction on the CQI-ReportPeriodicScell |
Samsung |
R2-2205202 |
Correction on the CQI-ReportPeriodicScell |
Samsung |
R2-2205203 |
Correction on the CQI-ReportPeriodicScell |
Samsung |
R2-2205427 |
Correction on evaluation of conditional reconfiguration |
CATT |
R2-2205544 |
Discussion on application layer measurement and reporting for LTE during full configuration |
Intel Corporation |
R2-2205545 |
Correction to application layer measurement and reporting for LTE during full configuration |
Intel Corporation |
R2-2205731 |
Correction to application layer measurement and reporting |
Google Inc., Qualcomm |
R2-2205733 |
Correction to application layer measurement and reporting |
Google Inc., Qualcomm |
R2-2205741 |
Correction to application layer measurement and reporting |
Google Inc., Qualcomm |
R2-2206003 |
Correction to application layer measurement and reporting for LTE during full configuration |
Intel Corporation |
R2-2206161 |
Report of [AT118-e][201][LTE] LTE legacy CRs (Samsung) |
Samsung |
R2-2206187 |
Correction to application layer measurement and reporting |
Google Inc., Qualcomm, Intel Corporation |
R2-2206188 |
Correction to application layer measurement and reporting |
Google Inc., Qualcomm, Intel Corporation |
R2-2206189 |
Correction to application layer measurement and reporting |
Google Inc., Qualcomm, Intel Corporation |
R2-2206372 |
LS on the CSI periodic reporting for Dormant SCell state |
RAN2 |
R2-2206686 |
Minor changes collected by Rapporteur |
Samsung |
5.1.1 |
Organisational |
|
R2-2204433 |
Reply LS on NR-U channel information and procedures (R1-2202673; contact: Samsung) |
RAN1 |
R2-2204434 |
Reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP (R1-2202691; contact: Apple) |
RAN1 |
R2-2204452 |
Reply LS on Intra UE Prioritization Scenario (R1-2202734; contact: vivo) |
RAN1 |
R2-2204503 |
Reply LS on power control for NR-DC (R4-2206566; contact: OPPO & vivo) |
RAN4 |
R2-2206470 |
Reply LS on PDCCH Blind Detection in CA (R1-2205320; contact: Huawei) |
RAN1 |
R2-2206741 |
LS on NPN only cell (R3-223928; contact: Huawei) |
RAN3 |
R2-2206760 |
Further Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R4-2210815; contact: Qualcomm) |
RAN4 |
R2-2206803 |
Reply LS on power control for NR-DC (R1-2205448; contact: Nokia) |
RAN1 |
R2-2206805 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R1-2205465; contact: Huawei) |
RAN1 |
R2-2206811 |
LS on New UE Feature for HARQ-ACK multiplexing on PUSCH in the absence of PUCCH (R1-2205634; contact: Apple) |
RAN1 |
5.1.2 |
Stage 2 corrections |
|
R2-2205923 |
Correction for SCell activation |
Huawei, HiSilicon |
R2-2205924 |
Correction for SCell activation |
Huawei, HiSilicon |
R2-2205950 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Ericsson |
R2-2205951 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Ericsson |
R2-2205978 |
Support of 1Tx-2Tx UL Tx switching for EN-DC |
Huawei, HiSilicon, China Telecom |
R2-2205979 |
Support of 1Tx-2Tx UL Tx switching for EN-DC |
Huawei, HiSilicon, China Telecom |
R2-2205990 |
Support of UL Tx switching for inter-band UL CA and SUL |
Huawei, HiSilicon, China Telecom |
R2-2206110 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Ericsson |
R2-2206111 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Ericsson |
R2-2206499 |
Report of [AT118-e][013][NR1516] Stage-2 (ZTE) |
ZTE Corporation (Rapporteur) |
R2-2206510 |
Correction for SCell activation |
Huawei, HiSilicon |
R2-2206511 |
Correction for SCell activation |
Huawei, HiSilicon |
R2-2206512 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Ericsson |
R2-2206513 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Ericsson |
R2-2206514 |
Support of 1Tx-2Tx UL Tx switching for EN-DC |
Huawei, HiSilicon, China Telecom |
R2-2206515 |
Support of 1Tx-2Tx UL Tx switching for EN-DC |
Huawei, HiSilicon, China Telecom |
R2-2206516 |
Support of UL Tx switching for inter-band UL CA and SUL |
Huawei, HiSilicon, China Telecom |
5.1.3 |
User Plane corrections |
|
R2-2206468 |
Offline 014: Rel-15/16 User Plane |
Samsung |
5.1.3.1 |
MAC |
|
R2-2204755 |
Clarification on SR and PUSCH collision |
OPPO, Samsung |
R2-2204756 |
Clarification on SR and PUSCH collision |
OPPO, Samsung |
R2-2204757 |
Clarification on SR and PUSCH collision |
OPPO, Samsung |
R2-2205682 |
CR for procedure level alignment of UL skipping |
Apple |
R2-2205717 |
Clarification on Duplication MAC CE |
Samsung |
R2-2205718 |
Clarification on Duplication MAC CE |
Samsung |
R2-2206694 |
Clarification on Duplication MAC CE |
Samsung, Apple, CATT, Nokia |
R2-2206695 |
Clarification on Duplication MAC CE |
Samsung, Apple, CATT, Nokia |
5.1.3.2 |
RLC PDCP SDAP BAP |
|
R2-2205715 |
CR for EHC decompression |
Samsung |
R2-2205716 |
CR for EHC decompression |
Samsung |
R2-2206696 |
CR for EHC decompression |
Samsung |
R2-2206697 |
CR for EHC decompression |
Samsung |
5.1.4.1 |
NR RRC |
|
R2-2206086 |
Miscellaneous non-controversial corrections Set XIV |
Ericsson |
R2-2206087 |
Miscellaneous non-controversial corrections Set XIV |
Ericsson |
R2-2206653 |
Report of [AT118-e][019][NR1516] CP Miscellanous |
vivo |
R2-2206821 |
Miscellaneous non-controversial corrections Set XIV |
Ericsson |
5.1.4.1.1 |
Connection control |
|
R2-2204411 |
LS on configuration of p-MaxEUTRA and p-NR-FR1 (R5-217995; contact: Huawei) |
RAN5 |
R2-2204453 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R1-2202769; contact: Huawei) |
RAN1 |
R2-2204504 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R4-2206567; contact: Huawei) |
RAN4 |
R2-2204648 |
Discussion on configuration of p-MaxEUTRA and p-NR-FR1 |
ZTE Corporation, Sanechips |
R2-2204649 |
[Draft] Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
ZTE Corporation |
R2-2204917 |
Discussion on RLC re-establishment issue upon DAPS fallback |
Huawei, HiSilicon |
R2-2204918 |
Correction on UE behaviours for DAPS fallback_Alt1 |
Huawei, HiSilicon |
R2-2204919 |
Correction on UE behaviours for DAPS fallback_Alt2 |
Huawei, HiSilicon |
R2-2204920 |
Correction on the RRC reestablishment in CHO |
Huawei, HiSilicon |
R2-2204921 |
Correction on the RRC reestablishment in CHO |
Huawei, HiSilicon |
R2-2205251 |
Corrections on BAP entity release in MR DC release procedure in TS 38.331 |
Huawei, HiSilicon |
R2-2205252 |
Corrections on BAP entity release in MR DC release procedures in TS 38.331 |
Huawei, HiSilicon |
R2-2205406 |
CR on 38.331 for sn-FieldLength |
ZTE Corporation,Sanechips |
R2-2205407 |
CR on 38.331 for sn-FieldLength |
ZTE Corporation,Sanechips |
R2-2205513 |
Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
Huawei, HiSilicon |
R2-2205586 |
SMTC configuration for target cell |
Lenovo (Beijing) Ltd |
R2-2205599 |
SMTC configuration for target cell |
Lenovo (Beijing) Ltd |
R2-2205614 |
SMTC configuration for target cell |
Lenovo |
R2-2205617 |
Correction to RRC reestablishment for IAB |
Google Inc. |
R2-2205624 |
Correction to RRC reestablishment for IAB |
Google Inc. |
R2-2205850 |
CHO configuration with SCG release |
Qualcomm Incorporated |
R2-2205858 |
CHO configuration with SCG release |
Qualcomm Incorporated |
R2-2205965 |
Correction of Need Code in IE SearchSpace |
Ericsson |
R2-2205966 |
Correction of Need Code in IE SearchSpace |
Ericsson |
R2-2205967 |
Correction of Need Code in IE SearchSpace |
Ericsson |
R2-2205968 |
WF for NS_55 in NR CA |
Ericsson |
R2-2206145 |
CHO configuration with SCG release |
Qualcomm Incorporated |
R2-2206146 |
CHO configuration with SCG release |
Qualcomm Incorporated |
R2-2206421 |
Summary of [AT118-e][015][NR1516] p-MaxEutra and p-NR-FR1 (Huawei) |
Huawei, HiSilicon |
R2-2206422 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
RAN2 |
R2-2206476 |
[AT118-e][016][NR1516] Connection Control I (Ericsson) |
Ericsson |
R2-2206518 |
Report of [AT118-e][017][NR1516] Connection Control II (Huawei) |
Huawei |
R2-2206645 |
Correction of Need Code in IE SearchSpace |
Ericsson |
R2-2206646 |
Correction of Need Code in IE SearchSpace |
Ericsson |
R2-2206647 |
Report [016][NR1516] Connection Control I, Final |
Ericsson |
R2-2206860 |
Corrections on BAP entity release in MR DC release procedures in TS 38.331 |
Huawei, HiSilicon |
5.1.4.1.2 |
RRM and Measurements |
|
R2-2204483 |
Reply LS to RAN2 on L3 filter configuration (R4-2207041; contact: Apple) |
RAN4 |
R2-2204611 |
38331CR Corrections on T321 and T322 timer start-R15 |
OPPO |
R2-2204612 |
38331CR Corrections on T321 and T322 timer start-R16 |
OPPO |
R2-2204613 |
38331CR Corrections on T321 and T322 timer start-R17 |
OPPO |
R2-2205294 |
Discussion on L3 filtering |
Huawei, HiSilicon |
R2-2205295 |
Correction to L3 filtering (R15) |
Huawei, HiSilicon |
R2-2205296 |
Correction to L3 filtering (R16) |
Huawei, HiSilicon |
R2-2205297 |
Correction to L3 filtering (R17) |
Huawei, HiSilicon |
R2-2205313 |
Correction on quantity configuration |
Xiaomi |
R2-2205314 |
Correction on quantity configuration |
Xiaomi |
R2-2205678 |
Clarification on L3 filtering configuration (filterCoefficient) |
Apple, Ericsson |
R2-2205961 |
Clarification on L3 filtering configuration (filterCoefficient) |
Apple, Ericsson |
R2-2206093 |
Clarification on L3 filtering configuration (filterCoefficient) |
Apple, Ericsson |
R2-2206576 |
Summary of [AT118-e][018][NR1516] RRM and measurements (Apple) |
Apple |
5.1.4.1.4 |
Inter-Node RRC messages |
|
R2-2204902 |
Confirmation for inter-MN HO without SN change |
NEC |
R2-2205428 |
Correction on FR1-FR1 power control parameters of NR-DC |
CATT |
R2-2205429 |
Correction on FR1-FR1power control parameters of NR-DC |
CATT |
5.1.4.1.5 |
Other |
|
R2-2204728 |
Correction on T345 for UAI overheating |
OPPO |
R2-2204729 |
Correction on T345 for UAI overheating |
OPPO |
R2-2204845 |
Correction on rrc-ConfiguredUplinkGrant in Rel-15 |
vivo |
R2-2204846 |
Correction on rrc-ConfiguredUplinkGrant in Rel-16 |
vivo |
R2-2205503 |
Need code correction for ReferenceTimeInfo |
Ericsson |
R2-2205504 |
Need code correction for ReferenceTimeInfo |
Ericsson |
R2-2205827 |
Correction on rrc-ConfiguredUplinkGrant in Rel-17 |
vivo |
R2-2205948 |
Miscellaneous corrections |
Lenovo |
R2-2206654 |
Correction on rrc-ConfiguredUplinkGrant in Rel-15 |
vivo |
R2-2206655 |
Correction on rrc-ConfiguredUplinkGrant in Rel-16 |
vivo |
R2-2206656 |
Correction on rrc-ConfiguredUplinkGrant in Rel-17 |
vivo |
R2-2206657 |
Need code correction for ReferenceTimeInfo |
Ericsson |
R2-2206658 |
Need code correction for ReferenceTimeInfo |
Ericsson |
5.1.4.2 |
LTE changes |
|
R2-2205298 |
Correction on NR serving frequency results reporting for event-triggered measurement (R15) |
Huawei, HiSilicon |
R2-2205299 |
Correction on NR serving frequency results reporting for event-triggered measurement (R16) |
Huawei, HiSilicon |
R2-2205300 |
Correction on NR serving frequency results reporting for event-triggered measurement (R17) |
Huawei, HiSilicon |
5.1.4.3 |
UE capabilities |
|
R2-2204419 |
LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#108-e (R1-2202764; contact: NTT DOCOMO) |
RAN1 |
R2-2204472 |
LS on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR (R4-2206828; contact: Apple) |
RAN4 |
R2-2204485 |
LS on UE capability for inter-frequency measurement without MG (R4-2207090; contact: Huawei) |
RAN4 |
R2-2204840 |
Correction to multi-DCI multi-TRP and new UE capability to limit PDCCH monitoring |
Intel Corporation |
R2-2204841 |
New UE capability to limit PDCCH monitoring |
Intel Corporation |
R2-2205118 |
Clarification on simultaneous Rx/Tx capability per band pair |
NTT DOCOMO, INC. |
R2-2205119 |
Clarification on simultaneous Rx/Tx capability per band pair |
NTT DOCOMO, INC. |
R2-2205121 |
Clarification on simultaneous Rx/Tx capability per band pair |
NTT DOCOMO, INC. |
R2-2205451 |
Correction on the UE capability description of the overlapping PDSCH in Rel-17 |
Xiaomi Communications, Samsung |
R2-2205452 |
Correction on the UE capability description of the overlapping PDSCH in Rel-16 |
Xiaomi Communications, Samsung |
R2-2205453 |
Clarification on the rmtc-Config-r16 |
Xiaomi Communications, Apple, OPPO |
R2-2205556 |
Correction on measurementEnhancement capability for high speed scenario |
Huawei, HiSilicon |
R2-2205557 |
Correction on measurementEnhancement capability for high speed scenario |
Huawei, HiSilicon |
R2-2205558 |
Correction on UE capability for inter-frequency measurement without MG |
Huawei, HiSilicon |
R2-2205559 |
Correction on UE capability for inter-frequency measurement without MG |
Huawei, HiSilicon |
R2-2205560 |
Clarification on capabilities reported in different granularity with prerequisite |
Huawei, HiSilicon |
R2-2205561 |
Clarification on capabilities reported in different granularity with prerequisite |
Huawei, HiSilicon |
R2-2205984 |
Clarifications on CHO and CPC UE capabilities |
Huawei, HiSilicon |
R2-2205985 |
Clarifications on CHO and CPC UE capabilities |
Huawei, HiSilicon |
R2-2206000 |
bwp-SwitchingDelay conditionally mandatory capability |
Qualcomm Incorporated, NTT DOCOMO INC. |
R2-2206001 |
bwp-SwitchingDelay conditionally mandatory capability |
Qualcomm Incorporated, NTT DOCOMO INC. |
R2-2206002 |
Clarification on configuredUL-GrantType1-v1650 |
Qualcomm Incorporated |
R2-2206063 |
Clarification on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR |
Apple Inc |
R2-2206064 |
Clarification on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR |
Apple Inc |
R2-2206406 |
Correction to multi-DCI multi-TRP and new UE capability to limit PDCCH monitoring |
Intel Corporation |
R2-2206407 |
New UE capability to limit PDCCH monitoring |
Intel Corporation |
R2-2206408 |
Correction to multi-DCI multi-TRP and new UE capability to limit PDCCH monitoring |
Intel Corporation |
R2-2206409 |
New UE capability to limit PDCCH monitoring |
Intel Corporation |
R2-2206434 |
Summary of [AT118-e][020][NR1516] UE capabilities I (NTT DOCOMO) |
NTT DOCOMO |
R2-2206435 |
Clarification on simultaneous Rx/Tx capability per band pair |
NTT DOCOMO, INC. |
R2-2206436 |
Clarification on simultaneous Rx/Tx capability per band pair |
NTT DOCOMO, INC. |
R2-2206437 |
Clarification on simultaneous Rx/Tx capability per band pair |
NTT DOCOMO, INC. |
R2-2206441 |
Clarification on configuredUL-GrantType1-v1650 |
Qualcomm Incorporated |
R2-2206442 |
Clarification on configuredUL-GrantType1-v1650 |
Qualcomm Incorporated |
R2-2206495 |
Clarification on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR |
Apple Inc. |
R2-2206496 |
Clarification on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR |
Apple Inc. |
R2-2206558 |
Clarification on miscellaneous UE capabilities |
Huawei, HiSilicon |
R2-2206559 |
Clarification on miscellaneous UE capabilities |
Huawei, HiSilicon |
R2-2206560 |
LS on eMIMO features defined in different granularity with prerequisite |
RAN2 |
R2-2206561 |
Summary of [AT118-e][021][NR1516] UE capabilities II (Huawei) |
Huawei, HiSilicon |
R2-2206585 |
Correction on the UE capability description of the overlapping PDSCH |
Xiaomi Communications, Samsung |
R2-2206586 |
Correction on the UE capability description of the overlapping PDSCH |
Xiaomi Communications, Samsung |
R2-2206659 |
Clarification on the rmtc-Config-r16 |
Xiaomi Communications |
R2-2206660 |
Clarification on the rmtc-Config-r16 |
Xiaomi Communications |
R2-2206843 |
bwp-SwitchingDelay conditionally mandatory capability |
Qualcomm Incorporated, NTT DOCOMO INC. |
R2-2206872 |
Clarification on the rmtc-Config-r16 |
Xiaomi Communications |
5.1.4.4 |
Idle/inactive mode procedures |
|
R2-2204482 |
Reply LS to RAN2 on RRM relaxation in power saving (R4-2207038; contact: CATT) |
RAN4 |
R2-2204826 |
Correction on RRM relaxation in PowSav |
vivo |
R2-2205476 |
Correction on RRM relaxation in PowSav |
vivo |
R2-2205742 |
Addressing inconsistency for RRM measurement rules |
Ericsson, CATT |
R2-2205743 |
Addressing inconsistency for RRM measurement rules |
Ericsson, CATT |
R2-2205945 |
Miscellaneous Editorial Corrections |
Qualcomm Incorporated |
R2-2205946 |
Miscellaneous Editorial Corrections |
Qualcomm Incorporated |
R2-2206446 |
Miscellaneous Editorial Corrections |
Qualcomm Incorporated (Rapporteur) |
R2-2206447 |
Miscellaneous Editorial Corrections |
Qualcomm Incorporated (Rapporteur) |
R2-2206449 |
[AT118-e][022][NR1516] Idle/Inactive mode (Qualcomm) |
Qualcomm Incorporated |
R2-2206699 |
Addressing inconsistency for RRM measurement rules |
Ericsson, CATT |
R2-2206700 |
Addressing inconsistency for RRM measurement rules |
Ericsson, CATT |
R2-2206701 |
Addressing inconsistency for RRM measurement rules |
Ericsson, CATT |
R2-2206702 |
Addressing inconsistency for RRM measurement rules |
Ericsson, CATT |
5.2.1 |
General and Stage-2 corrections |
|
R2-2204454 |
Reply LS to RAN4 on PEMAX for NR-V2X (R1-2202816; contact: Huawei) |
RAN1 |
R2-2204513 |
LS on V2X PC5 link for unicast communication with null security algorithm (R5-222035; contact: HiSilicon) |
RAN5 |
R2-2204516 |
Reply LS on how to receive the first PC5-S unicast message during PC5-S connection setup procedure (S2-2203024; contact: CATT) |
SA2 |
R2-2206758 |
Reply LS on signalling of PC2 V2X intra-band con-current operation (R4-2210733; contact: CATT) |
RAN4 |
R2-2206796 |
Reply LS on V2X PC5 link for unicast communication with null security algorithm (C1-223972; contact: Huawei) |
CT1 |
5.2.2 |
Control plane corrections |
|
R2-2204572 |
Correction on field description of sl-DefaultTxConfigIndex |
OPPO |
R2-2204573 |
Correction on field description of sl-DefaultTxConfigIndex |
OPPO |
R2-2204645 |
Correction on per-FS capability |
OPPO |
R2-2204646 |
Correction on per-FS capability |
OPPO |
R2-2204844 |
Discussion on null security algorithm |
ZTE Corporation, Sanechips |
R2-2204855 |
Summary of Rel-16 control plane corrections |
Huawei, HiSilicon |
R2-2204856 |
Miscelleneous corrections |
Huawei, HiSilicon |
R2-2204857 |
Miscelleneous corrections |
Huawei, HiSilicon |
R2-2204858 |
[Draft] Reply LS on V2X PC5 link for unicast communication with NULL security algorithm |
Huawei, HiSilicon |
R2-2204859 |
Clarification on PC5 AS security |
Huawei, HiSilicon |
R2-2204860 |
Clarification on PC5 AS security |
Huawei, HiSilicon |
R2-2205108 |
(draft)reply LS on null security algorithm |
ZTE Corporation, Sanechips |
R2-2205109 |
Clarification on power control parameter |
ZTE Corporation, Sanechips,vivo |
R2-2205577 |
Clarifying support of null security algorithm for SL-SRB2 and SL-SRB3 |
MediaTek Inc. |
R2-2205578 |
Clarifying support of null security algorithm for SL-SRB2 and SL-SRB3 |
MediaTek Inc. |
R2-2205947 |
Miscellaneous corrections |
Lenovo |
R2-2205953 |
Miscellaneous corrections |
Lenovo |
R2-2206043 |
Correction on SUI message |
OPPO |
R2-2206281 |
Miscellaneous corrections on TS 38.331 for NR V2X |
OPPO |
R2-2206282 |
Miscellaneous corrections on TS 38.331 for NR V2X |
OPPO |
R2-2206283 |
Correction on per-FS capability |
OPPO |
R2-2206284 |
Correction on per-FS capability |
OPPO |
R2-2206285 |
Summary [AT118-e][701][V2X/SL] Miscellaneous corrections (OPPO) |
OPPO |
R2-2206630 |
Miscellaneous corrections on TS 38.331 for NR V2X |
OPPO, Huawei, HiSilicon, Lenovo |
R2-2206631 |
Miscellaneous corrections on TS 38.331 for NR V2X |
OPPO, Huawei, HiSilicon, Lenovo |
5.2.3 |
User plane corrections |
|
R2-2204774 |
PDCPRLC Entity Maintenance for SL-SRBs |
CATT |
R2-2204775 |
Corrections on MAC filtering issue for the first unicast PC5-S signalling |
CATT |
R2-2204776 |
Corrections on RLC entity establishment issue for the first unicast PC5-S signalling |
CATT |
R2-2204777 |
Corrections on PDCP entity establishment issue for the first unicast PC5-S signalling |
CATT |
R2-2204778 |
Correction on user plane aspects (Rapporteur CR) |
LG Electronics France |
R2-2205125 |
Corrections on SL configured grant and SL BSR |
ASUSTeK |
R2-2205126 |
TB filtering in MAC |
ASUSTeK |
R2-2205127 |
TB filtering in MAC |
ASUSTeK |
R2-2205144 |
Summary of MAC corrections (Rapporteur) |
LG Electronics France |
R2-2205602 |
Correction on PDCP SN setting for SLRB transmit operation |
Samsung |
R2-2205603 |
Correction on PDCP SN setting for SLRB transmit operation |
Samsung |
R2-2206286 |
Corrections on the MAC filtering for SL-SRB0/SL-SRB1 |
CATT |
R2-2206287 |
Corrections on the MAC filtering for SL-SRB0/SL-SRB1 |
CATT |
R2-2206288 |
Corrections on the receiving RLC entity establishment for SL-SRB0/SL-SRB1 |
CATT |
R2-2206289 |
Corrections on the receiving RLC entity establishment for SL-SRB0/SL-SRB1 |
CATT |
R2-2206290 |
Corrections on receiving PDCP entity establishment for SL-SRB0/SL-SRB1 |
CATT |
R2-2206291 |
Corrections on receiving PDCP entity establishment for SL-SRB0/SL-SRB1 |
CATT |
R2-2206292 |
Maintenance of SL-SRBs |
CATT |
R2-2206293 |
Corrections on SL BSR |
ASUSTeK |
R2-2206294 |
Corrections on SL BSR |
ASUSTeK |
R2-2206295 |
[AT118-e][703][V2X/SL] MAC corrections (ASUSTeK) |
ASUSTeK |
R2-2206298 |
[AT118-e][704][V2X/SL] PDCP corrections |
Samsung |
5.3.1 |
General and Stage 2 corrections |
|
R2-2204694 |
Correction on the description of deferred MT-LR |
CATT |
R2-2204695 |
Correction on the description of deferred MT-LR |
CATT |
R2-2206578 |
Correction on the description of deferred MT-LR |
CATT |
R2-2206579 |
Correction on the description of deferred MT-LR |
CATT |
5.3.3 |
LPP corrections |
|
R2-2205801 |
Motivation to clarify LPP segmentation purpose |
Ericsson |
R2-2205802 |
Clarification on LPP segmentation |
Ericsson |
R2-2205803 |
Clarification on LPP segmentation |
Ericsson |
5.4.3 |
RRC corrections |
|
R2-2204548 |
Corrections to SON/MDT capabilities |
Lenovo |
R2-2204549 |
Corrections to SON/MDT capabilities |
Lenovo |
R2-2204589 |
Corrections on LTE UE RLF Report |
China Telecom, CATT, Ericsson, ZTE |
R2-2204594 |
Corrections on LTE UE RLF Report |
China Telecom, CATT, Ericsson, ZTE |
R2-2204595 |
Corrections on LTE UE RLF Report |
China Telecom, CATT, Ericsson, ZTE |
R2-2204916 |
Correction on delay value configuration description |
Huawei, HiSilicon |
R2-2204937 |
Add TAC into Previous Cell Information of RLF Report |
CATT |
R2-2205660 |
Addition of missing information into RA-InformationCommon-r16 |
Apple, Ericsson |
R2-2205661 |
Addition of missing information into RA-InformationCommon-r16 |
Apple, Ericsson |
R2-2205760 |
Discrepancy on inclusion of reconnectCellId |
Samsung Electronics Co., Ltd |
R2-2205885 |
On DAPS handover failure handling |
Ericsson |
R2-2205886 |
On sensor information configuration |
Ericsson |
R2-2205887 |
On sensor information configuration |
Ericsson |
R2-2205888 |
On including SSB and CSI-RS measurements in RLF report |
Ericsson |
R2-2205889 |
On including SSB and CSI-RS measurements in RLF report |
Ericsson |
R2-2205890 |
On ObtainCommonLocation related configuration |
Ericsson |
R2-2205891 |
On ObtainCommonLocation related configuration |
Ericsson |
R2-2206106 |
Add TAC into Previous Cell Information of RLF Report |
CATT |
R2-2206107 |
Add TAC into Previous Cell Information of RLF Report |
CATT |
R2-2206692 |
SON-MDT changes agreed in RAN#118 meeting |
Ericsson |
6.0.1 |
RRC |
|
R2-2204418 |
LS on updated Rel-17 LTE and NR higher-layers parameter list (R1-2202760; contact: Ericsson) |
RAN1 |
R2-2204986 |
[H585] Correction for new IE for TimeAlignmentTimer |
Huawei, HiSilicon |
R2-2205002 |
[H581][Z141][M607] Correction for pre-configured MG for POS |
Huawei, HiSilicon |
R2-2205015 |
[H634] Correction for the need code and conditions for optional fields in PC5 RRC message |
Huawei, HiSilicon |
R2-2205196 |
Discussion on RIL issue E133 |
Ericsson |
R2-2205392 |
[N129] Corrections to FR2 UL gaps |
Nokia, Nokia Shanghai Bell |
R2-2205397 |
Discussion on PDCCH adaptation IEs (related to N128/Z054/Z055) |
Nokia, Nokia Shanghai Bell |
R2-2205419 |
On Rel-17 ASN.1 review process |
Nokia, Nokia Shanghai Bell |
R2-2205433 |
[N108] IE structures for L1 parameters |
Nokia, Nokia Shanghai Bell |
R2-2205434 |
[N104] Survey of Rel-17 Need S fields |
Nokia, Nokia Shanghai Bell |
R2-2205684 |
Discussion on ul-AccessConfigListDCI (RIL A402, A405) |
Apple |
R2-2205969 |
NR Rel-17 ASN1 review file |
Ericsson |
R2-2205970 |
NR Re-17 RIL list |
Ericsson |
R2-2205971 |
NR Rel-17 Class0 issues |
Ericsson |
R2-2206084 |
ASN1 review general corrections |
Ericsson |
R2-2206085 |
RIL list General ASN1 issues |
Ericsson |
R2-2206131 |
PDSCH and PUSCH TDRA configuration (RIL: Q300, E057) |
Huawei, HiSilicon |
R2-2206225 |
Consolidated RIL List Rel-17 ASN.1 review |
Ericsson |
R2-2206262 |
Correction for the need code and conditions for optional fields in PC5 RRC message |
Huawei, HiSilicon |
R2-2206263 |
Correction for the need code and conditions for optional fields in PC5 RRC message |
Huawei, HiSilicon |
R2-2206567 |
Report of [AT118-e][024][NR17] RRC II (Nokia) |
Nokia (Rapporteur) |
R2-2206605 |
Summary of offline discussion: [AT118-e][025][NR17] RRC issues (Huawei) |
Huawei, HiSilicon |
R2-2206606 |
Draft CR for TDRA configuration modifications |
Huawei, HiSilicon |
R2-2206683 |
Implementing agreement on [Q302] from ASN.1 ad hoc |
Qualcomm Inc. |
R2-2206720 |
Corrections to searchSpaceSwitchTimer and pdcch-SkippingDurationList |
Nokia, Nokia Shanghai Bell |
R2-2206773 |
Corrections to searchSpaceSwitchTimer and pdcch-SkippingDurationList |
Nokia, Nokia Shanghai Bell |
R2-2206822 |
[Post118-e][023][NR17] RRC (Ericsson) |
Ericsson |
R2-2206848 |
ASN1 review general corrections |
Ericsson |
R2-2206883 |
ASN1 review general corrections |
Ericsson |
6.0.2 |
UE capabilities |
|
R2-2204427 |
LS on updated Rel-17 RAN1 UE features list for NR (R1-2202927; contact: NTT DOCOMO, AT&T)) |
RAN1 |
R2-2204471 |
LS on Rel-17 RAN4 UE feature list for NR (R4-2206572; contact: CMCC) |
RAN4 |
R2-2204838 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) |
Intel Corporation |
R2-2204839 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
Intel Corporation |
R2-2205657 |
Introduction of FR2 UL gap UE capability |
Apple, Huawei, HiSilicon |
R2-2205658 |
Introduction of FR2 UL gap UE capability |
Apple, Huawei, HiSilicon |
R2-2206440 |
LS on Rel-17 RAN4 UE feature list for NR (R4-2210437; contact: CMCC) |
RAN4 |
R2-2206459 |
Introduction of FR2 UL gap UE capability |
Apple, Huawei, HiSilicon |
R2-2206460 |
Introduction of FR2 UL gap UE capability |
Apple, Huawei, HiSilicon |
R2-2206472 |
LS on updated Rel-17 RAN1 UE features list for NR (R1-2205328; contact: NTT DOCOMO, AT&T) |
RAN1 |
R2-2206474 |
Reply LS on updated Rel-17 RAN1 UE features list for NR (R1-2205341; contact: vivo) |
RAN1 |
R2-2206498 |
NCSG MG issue |
Intel Corporation |
R2-2206651 |
Report [023][NR17] RRC I (Ericsson)Final |
Ericsson |
R2-2206671 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) |
Intel Corporation |
R2-2206672 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
Intel Corporation |
R2-2206765 |
LS on Rel-17 RAN4 UE feature list for NR (R4-2211190; contact: CMCC) |
RAN4 |
R2-2206847 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
Intel Corporation |
R2-2206849 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) |
Intel Corporation |
6.0.3 |
Gaps Coordination |
|
R2-2205290 |
Discussion on gap priority |
Huawei, HiSilicon |
R2-2205768 |
Consideration on gap priorities |
ZTE Corporation, Sanechips |
R2-2206011 |
Gaps coordination |
Ericsson |
R2-2206452 |
Report of [AT118-e][027][NR17] Gap Coordination (MediaTek) |
MediaTek Inc. |
R2-2206756 |
LS reply on coordination of R17 gap features (R4-2210624; contact: MediaTek) |
RAN4 |
6.0.4 |
Other |
|
R2-2204887 |
LCP priority of MAC CEs |
LG Electronics Inc. |
R2-2205261 |
Discussion on LCP Priority of Rel-17 MAC CEs |
vivo |
R2-2205853 |
Discussion on RAN2 signalling alternatives |
Ericsson |
R2-2206038 |
Cross WI coordination on LCP prioritization for UL MAC Ces |
Huawei, HiSilicon |
R2-2206489 |
[AT118-e][028][NR17] Summary of Priority of MAC Ces |
LG Electronics Inc. |
R2-2206490 |
Priority of MAC CEs |
LG Electronics Inc. |
6.1.1.1 |
Organizational |
|
R2-2204456 |
Reply LS on Multicast paging with TMGI (S3-220537; contact: Huawei) |
SA3 |
R2-2204497 |
LS on further outstanding issues in TS 23.247 (R3-222867; contact: Ericsson) |
RAN3 |
R2-2204511 |
LS on parameters preconfigured in the UE to receive MBS service (CP-220398; contact: Qualcomm) |
CT |
R2-2204517 |
Reply LS on maximum number of MBS sessions that can be associated to a PDU session (S2-2203050; contact: Ericsson) |
SA2 |
R2-2206338 |
Response LS on maximum number of MBS sessions that can be associated to a PDU session (S4-220567; contact: Ericsson) |
SA4 |
R2-2206473 |
LS on NR MBS TP for TS 38.300 (R1-2205336; contact: Huawei) |
RAN1 |
R2-2206550 |
Reply LS on HARQ process for MCCH and Broadcast MTCH(s) (R1-2205215; contact: BBC) |
RAN1 |
R2-2206551 |
LS on TCI indication in multicast DCI (R1-2205369; contact: CMCC) |
RAN1 |
6.1.1.3 |
CR Rapporteur Resolutions |
|
R2-2205455 |
Miscellaneous corrections for MBS 38.323 |
Xiaomi Communications |
R2-2205938 |
MBS corrections for TS 38.331 |
Huawei, HiSilicon |
R2-2206120 |
Rapporteur proposed resolutions for MBS related RIL issues |
Huawei, HiSilicon |
R2-2206610 |
MBS corrections for TS 38.331 |
Huawei, HiSilicon |
R2-2206719 |
Rapporteur proposed resolutions for MBS related RIL issues |
Huawei, HiSilicon |
6.1.3 |
Corrections |
|
R2-2205454 |
Discussion on the HFN issue for multicast |
Xiaomi Communications |
6.1.3.1 |
Control Plane |
|
R2-2204555 |
MBS reception interruption problem in LTE and SFN in NR MBS |
TD Tech Ltd |
R2-2204604 |
[RIL-O400]-MII reporting after Handover |
OPPO |
R2-2204605 |
[RIL-O400]-38331CR-MII reporting after handover |
OPPO |
R2-2204606 |
[RIL-O404]-38321CR-MTCH reception in beam sweeping |
OPPO |
R2-2204607 |
[RIL-O404]-38331CR-MTCH reception in beam sweeping |
OPPO |
R2-2204608 |
[RIL-O406] Discussion on broadcast reception over Scell |
OPPO |
R2-2204624 |
NR MBS UAC enhancement aspects |
Qualcomm Inc |
R2-2204668 |
Correction to 38.304 for MBS |
CATT, CBN |
R2-2204669 |
[C006] Correction to UE Behavior on Group Paging Handling |
CATT |
R2-2204670 |
[C001] Modificaitons towards the MRB ID Change Procedure |
CATT |
R2-2204671 |
[C003] Specify the UE Behaviour for Broadcast MRB Modification |
CATT |
R2-2204681 |
[C003] Discussion on UE behavior for Broadcast MRB Modification |
CATT, CBN |
R2-2204682 |
[C009][C010] On broadcast reception on SCell |
CATT |
R2-2204743 |
Discussion on MBS UAC Enhancements |
Spreadtrum Communications |
R2-2204827 |
[V500] Clarification on Group Paging for INACTIVE UE |
vivo |
R2-2204828 |
[V503][V504][V508] Correction on MRB Handling |
vivo |
R2-2204829 |
[V530]-[V532] Correction on MCCH Acquisition |
vivo |
R2-2204830 |
[V533] Correction on Logical Channel Setup for PTM Transmission |
vivo |
R2-2205111 |
Clarification of “providing SIB20” in TS38.304 |
Kyocera |
R2-2205112 |
Frequency of interest in MBS Interest Indication |
Kyocera |
R2-2205174 |
Discussion on broadcast reception over SCell |
OPPO Beijing |
R2-2205215 |
RIL406: Configuration restriction for broadcast reception on SCell |
OPPO Beijing |
R2-2205249 |
MRB addition and modification (RIL: V503, H002, H003) |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
R2-2205458 |
RIL(X305) Discussion on the number of MRBs mapped to a MBS session |
Xiaomi Communications |
R2-2205461 |
UAC for MBS |
Samsung R&D Institute India |
R2-2205462 |
[O406], [H006] MII Reporting |
Samsung R&D Institute India |
R2-2205539 |
[I201] MCCH modification period and notification |
Intel Corporation |
R2-2205626 |
[H001, H005, Z608, C005] Discussion on multicast MRB and DRB in RRC |
ZTE, Sanechips |
R2-2205627 |
Miscellaneous correction to TS 38331 |
ZTE, Sanechips |
R2-2205632 |
[C001, H002, v503, Z609] MRB ID scope and its modification on the fly |
ZTE, Sanechips |
R2-2205671 |
Broadcast MBS reception on SCell (RIL A021) |
Apple |
R2-2205712 |
Discussion on MRB Configuration |
Samsung |
R2-2205744 |
Broadcast session start and MCCH |
Ericsson |
R2-2205745 |
Frequency prioritization |
Ericsson |
R2-2205747 |
MBS Interested Indication |
Ericsson |
R2-2205749 |
Multicast session start and Paging |
Ericsson |
R2-2206091 |
[H006]Discussion on MII for MBS broadcast reception on SCell |
Huawei, HiSilicon |
R2-2206108 |
Discussion on MBS Interest Indication |
TCL Communication Ltd. |
R2-2206121 |
Discussion on rate matching resources for unicast and MBS (RIL: H093) |
Huawei, HiSilicon |
R2-2206122 |
Discussion on configuration of additional common CORESET for MBS broadcast in RRC Connected mode (RIL: H009) |
Huawei, HiSilicon |
R2-2206123 |
Corrections for GroupConfig structure (RIL: H091) |
Huawei, HiSilicon |
R2-2206124 |
Draft LS on AS-NAS layer interactions for MBS |
Huawei, HiSilicon |
R2-2206159 |
SIB20 signalling issues including optionality for cfr-ConfigMCCH-MTCH-r17 |
Qualcomm Incorporated |
R2-2206380 |
Report of [AT118-e][030][MBS] CP other |
CATT |
R2-2206423 |
Summary of offline discussion: [AT118-e][029][MBS] CP Broadcast (Huawei) |
Huawei, HiSilicon |
R2-2206607 |
Summary of offline discussion: [AT118-e][029][MBS] CP Broadcast (Huawei) |
Huawei, HiSilicon |
R2-2206608 |
LS on rate matching patterns and CORESET configuration for MBS |
RAN2 |
R2-2206609 |
LS on AS-NAS layer interactions for MBS |
RAN2 |
6.1.3.2 |
User Plane |
|
R2-2204609 |
38321CR-Corrections on MCCH and MTCH reception |
OPPO |
R2-2204626 |
R17 MBS UP remaining issues |
Qualcomm India Pvt Ltd |
R2-2204667 |
Consideration on MAC Remaining Issues of MBS |
CATT |
R2-2204683 |
Consideration on PDCP Remaining Issues of MBS |
CATT |
R2-2204744 |
Corrections on MBS |
Spreadtrum Communications |
R2-2204831 |
Discussion on CSI-mask Configuration with Multicast DRX |
vivo |
R2-2204832 |
Discussion on the Coexistence of DCP and Multicast DRX |
vivo |
R2-2204833 |
Correction on DL Data Transfer for MBS |
vivo |
R2-2204834 |
Correction on Multicast DRX |
vivo |
R2-2204891 |
Discussion on the impact of CSI and SRS due to multicast DRX |
NEC Europe Ltd |
R2-2204904 |
The timing for broadcast DRX and editorial corrections for multicast DRX |
OPPO |
R2-2204905 |
Corrections on CSI-mask and DCP coexistence for multicast DRX |
MediaTek inc. |
R2-2204906 |
Discussion on HFN negative value for multicast |
MediaTek inc. |
R2-2204969 |
Remaining issues on MBS user plane |
Lenovo |
R2-2205035 |
Discussion on CSI and SRS reporting issues |
CMCC |
R2-2205122 |
Clarification on MBS MAC subPDU discard |
LG Electronics Inc., Nokia, Nokia Shanghai Bell |
R2-2205128 |
Discussion on unicast retransmission for MBS transmission |
ASUSTeK |
R2-2205129 |
Handling of MAC PDU for MBS with Reserved LCID |
ASUSTeK |
R2-2205154 |
CSI Mask for MBS |
Nokia, Nokia Shanghai Bell |
R2-2205155 |
Setting of RX_DELIV for MBS |
Nokia, Nokia Shanghai Bell |
R2-2205156 |
DCP monitoring/WUS and MBS DRX and miscellaneous corrections to DRX |
Nokia, Nokia Shanghai Bell |
R2-2205218 |
[RIL406]The timing for broadcast DRX and SCell deactivation restriction |
OPPO Beijing |
R2-2205437 |
HARQ Process Handling for MBS Broadcast |
Samsung R&D Institute India |
R2-2205447 |
MBS Broadcast Retention |
Samsung R&D Institute India |
R2-2205449 |
WUS and DCP monitoring for MBS Multicast |
Samsung R&D Institute India |
R2-2205457 |
Clarification on the HARQ process used for broadcast MBS |
Xiaomi Communications |
R2-2205479 |
Further discussion on how to prevent negative HFN |
Huawei, HiSilicon |
R2-2205480 |
Remaining issues on CSI reporting for multicast |
Huawei, HiSilicon |
R2-2205481 |
Clarification on DRX timers for multicast |
Huawei, HiSilicon |
R2-2205483 |
Correction on the figures of MAC structure overview |
Huawei, HiSilicon |
R2-2205540 |
Remaining MBS user plane open issues |
Intel Corporation |
R2-2205628 |
CSI and SRS reporting in MBS DRX |
ZTE, Sanechips |
R2-2205629 |
Correction on CSI and SRS reporting for multicast DRX to 38321 |
ZTE, Sanechips |
R2-2205630 |
Remaining issues in PDCP layer for NR MBS |
ZTE, Sanechips |
R2-2205673 |
Leftover issues on multicast DRX mechanism |
Apple |
R2-2205709 |
Discussion on CSI reporting due to multicast DRX |
LG Electronics Inc. |
R2-2205713 |
Remaining Issues on Multicast DRX |
Samsung |
R2-2205714 |
Correction of PDCP for MBS |
Samsung |
R2-2205748 |
Multicast and CSI, SRS and DCP |
Ericsson |
R2-2206353 |
[AT118-e][032][MBS] PDCP (Xiaomi) |
Xiaomi |
R2-2206403 |
[AT118-e][031][MBS] MAC (OPPO) |
OPPO |
R2-2206556 |
[AT118-e][031][MBS] MAC (OPPO) |
OPPO |
R2-2206587 |
Part 2 summary of [AT118-e][032][MBS] PDCP (Xiaomi) |
Xiaomi |
R2-2206623 |
Corrections on MBS |
OPPO, Huawei, Nokia, Samsung, vivo |
R2-2206624 |
MBS SPS configuration on Scell |
RAN2 |
R2-2206648 |
MBS SPS configuration on Scell |
RAN2 |
R2-2206771 |
Corrections on MBS |
OPPO, Huawei, Nokia, Samsung, vivo |
R2-2206816 |
PDCP Corrections for MBS |
Xiaomi Communications |
6.1.4 |
UE capabilities |
|
R2-2204625 |
R17 MBS UE capabilities |
Qualcomm India Pvt Ltd |
R2-2204907 |
Discussion on mandatory ROHC support for MBS broadcast |
MediaTek inc. |
R2-2205541 |
Remaining MBS UE capability open issues |
Intel Corporation |
R2-2205746 |
Impact of MBS broadcast on paging and SIBs |
Ericsson |
R2-2205750 |
UE capabilities for MBS |
Ericsson |
R2-2205855 |
UE support for ROHC profiles and context sessions |
Ericsson |
R2-2205939 |
Discussion on UE capabilities for MBS |
Huawei, HiSilicon |
R2-2206109 |
Discussion on R17 MBS UE capability open issues |
TCL Communication Ltd. |
R2-2206114 |
UE capability discussion for MBS |
Xiaomi Communications |
R2-2206405 |
Summary of email discussion [AT118-e] [033] MBS UE capability |
MediaTek Inc. |
R2-2206520 |
Summary of Part 2 email discussion [AT118-e] [033] MBS UE capability |
nnMediaTek Inc. |
R2-2206521 |
Draft 38.306 CR for MBS UE capability corrections |
MediaTek Inc. |
R2-2206580 |
Summary of Part 2 email discussion [AT118-e] [033] MBS UE capability |
nnMediaTek Inc. |
R2-2206635 |
Draft 38.306 CR for MBS UE capability corrections |
MediaTek Inc. |
6.1.5 |
Other |
|
R2-2204647 |
R17 MBS power saving enhancement aspect |
Shanghai Jiao Tong University |
R2-2205338 |
UE based PTM to PTP switch |
Sony |
R2-2205456 |
Introduction of MBS for MRDC |
Xiaomi Communications |
R2-2205482 |
Correction on Stage 2 specs |
Huawei, HiSilicon |
R2-2205484 |
Addition of MBS related clarifications in 37340 |
Huawei, HiSilicon |
R2-2205625 |
Miscellaneous correction to TS 38300 |
ZTE, Sanechips |
R2-2205631 |
[Z606, Z607] Discussion on SDAP for NR MBS |
ZTE, Sanechips |
R2-2205672 |
Clarification on the support of MBS in MR-DC |
Apple |
R2-2206404 |
[AT118-e][034][MBS] Other |
ZTE |
R2-2206517 |
[AT118-e][034][MBS] Other |
ZTE |
R2-2206674 |
Summary of [AT118-e][034][MBS] Other (ZTE) |
ZTE |
R2-2206815 |
Corrections on MBS |
ZTE |
6.2.1 |
Organizational |
|
R2-2204435 |
Reply LS on RAN2 agreements for TRS-based Scell activation (R1-2202706; contact: Huawei) |
RAN1 |
R2-2204479 |
LS reply on UE behaviour for deactivated SCG and value range for measCycle (R4-2207019; contact: Ericsson) |
RAN4 |
R2-2204493 |
Reply LS on CPAC (R3-222754; contact: Lenovo) |
RAN3 |
R2-2204546 |
Corrections on TS 37.340 for DCCA enhancements |
ZTE Corporation, Sanechips, CATT |
R2-2205796 |
[Z012] Value range for measCyclePSCell |
Ericsson, ZTE Corporation |
R2-2205925 |
Introduction of further MRDC enhancements |
Huawei, HiSilicon |
R2-2205930 |
Issue list for 36.331 |
Huawei, HiSilicon |
R2-2205931 |
Issue list for 38.331 |
Huawei, HiSilicon |
R2-2205936 |
Corrections on further MRDC enhancements |
Huawei, HiSilicon |
R2-2205937 |
Corrections on further MRDC enhancements |
Huawei, HiSilicon |
R2-2206142 |
Summary of [Pre118-e][203][DCCA] 38331 36331 CRs and rapporteur resolutions (Huawei) |
Huawei, HiSilicon |
R2-2206162 |
Corrections on further MRDC enhancements |
Huawei, HiSilicon |
R2-2206163 |
Corrections on further MRDC enhancements |
Huawei, HiSilicon |
R2-2206164 |
Corrections on TS 37.340 for DCCA enhancements |
ZTE Corporation, Sanechips, CATT |
R2-2206265 |
Corrections for further MRDC enhancements |
Huawei, HiSilicon |
R2-2206266 |
Corrections for further MRDC enhancements |
Huawei, HiSilicon |
R2-2206368 |
Miscellaneous RRC issues in [220] |
Huawei, HiSilicon |
R2-2206603 |
Report of [AT118-e][221][DCCA] Stage-2 CRs for DCCA enhancements |
ZTE Corporation |
R2-2206704 |
Corrections on TS 37.340 for DCCA enhancements |
ZTE Corporation, Sanechips, CATT, Ericsson |
R2-2206829 |
Corrections on TS 37.340 for DCCA enhancement |
ZTE Corporation, Sanechips, CATT, Ericsson |
6.2.2 |
Efficient activation / deactivation mechanism for one SCG and SCells |
|
R2-2204621 |
(TP for CR to TS 38.331) Efficient SCG deactivation/activation |
Qualcomm Incorporated |
R2-2204754 |
Discussion on SCG activation |
Spreadtrum Communications |
R2-2204909 |
Beam failure detection upon SCG deactivation |
Fujitsu |
R2-2204910 |
[F001] Beam failure detection upon SCG deactivation |
Fujitsu |
R2-2204956 |
MAC related issues upon SCG activation and deactivation |
Lenovo |
R2-2205057 |
MAC correction on eDCCA |
vivo |
R2-2205058 |
Discussion on MAC remaining issue |
vivo |
R2-2205060 |
Discussion on SCG activation/deactivation processing |
vivo |
R2-2205061 |
Discussion on PDCP duplication handling while SCG is deactivated |
vivo |
R2-2205062 |
Discussion on whether cause value is needed in the SCG deactivation preference reporting |
vivo |
R2-2205245 |
37.340 corrections regarding deactivated SCG |
Nokia, Nokia Shanghai Bell |
R2-2205246 |
38.331 corrections on deactivated SCG |
Nokia, Nokia Shanghai Bell |
R2-2205247 |
Correction to deactivated SCG UL SRB3 handling |
Nokia, Nokia Shanghai Bell |
R2-2205248 |
38.321 corrections on deactivated SCG |
Nokia, Nokia Shanghai Bell |
R2-2205259 |
Network behaviour at/while SCG deactivation |
Fujitsu |
R2-2205260 |
Remaining issues on UL data arrival for SCG |
Fujitsu |
R2-2205273 |
Remaining issues for BFD indication in deactivated SCG |
Sharp |
R2-2205274 |
CR on 38.321 for Remaining issues for BFD indication in deactivated SCG |
Sharp |
R2-2205275 |
Remaining issues for configured grant Type 1 in deactivated SCG |
Sharp |
R2-2205276 |
CR on 38.321 for Remaining issues for configured grant Type 1 in deactivated SCG |
Sharp |
R2-2205277 |
RACH-less SCG activation by SCG activation command with BFD RS change |
Sharp |
R2-2205278 |
CR on 38.331 for RACH-less SCG activation by SCG activation command with BFD RS change |
Sharp |
R2-2205279 |
CR on 38.321 for RACH-less SCG activation by SCG activation command with BFD RS change |
Sharp |
R2-2205280 |
[J006] Correction of BFD procedure |
Sharp |
R2-2205367 |
Corrections on eDCCA |
vivo |
R2-2205422 |
Discussion on Beam Failure Information for Deactivated SCG |
CATT |
R2-2205423 |
Discussion on PDCP Duplication for SCG Deactivation |
CATT |
R2-2205424 |
Discussion on SCG Activation and Deactivation Indication to Lower Layer |
CATT |
R2-2205797 |
[E129] Stop/resume BFD at beam failure for deactivated SCG |
Ericsson |
R2-2205798 |
[E130] Cause values for UAI indicating preference for SCG deactivation |
Ericsson |
R2-2205799 |
[E131] Handling of UAI for deactivated SCG |
Ericsson |
R2-2205800 |
[E035] Define the content of TCI-Info |
Ericsson |
R2-2205926 |
Corrections for SCG (de)activation |
Huawei, HiSilicon |
R2-2205928 |
Discussion on the Editor notes of SCG(de)activation in 38.321 |
Huawei, HiSilicon |
R2-2205929 |
Correction on 38.321 |
Huawei, HiSilicon |
R2-2205932 |
[38.331 - H061] Performing SCG activation/deactivation at the right step |
Huawei, HiSilicon |
R2-2205949 |
On RACH resources for SCG activation |
InterDigital |
R2-2206165 |
Report of [AT118-e][222][DCCA] MAC/PDCP corrections for DCCA enhancements (Nokia) |
Nokia |
R2-2206166 |
Report of [AT118-e][223][DCCA] BFD corrections for DCCA enhancements (Fujitsu) |
Fujitsu |
R2-2206167 |
Report of [AT118-e][224][DCCA] RRC for SCG deactivation (Huawei) |
Huawei, HiSilicon |
R2-2206375 |
38.321 corrections on deactivated SCG |
Nokia, Nokia Shanghai Bell |
R2-2206377 |
38.321 corrections on deactivated SCG |
Nokia, Nokia Shanghai Bell |
R2-2206379 |
Corrections to MAC regarding deactivated SCG |
Nokia, Nokia Shanghai Bell |
R2-2206562 |
38.321 corrections on deactivated SCG |
Nokia, Nokia Shanghai Bell |
6.2.3 |
Conditional PSCell change / addition |
|
R2-2204623 |
(TP for CR to TS 38.331) Conditional PSCell change/addition |
Qualcomm Incorporated |
R2-2204801 |
Discussion RRCReconfiguration for CPC and CHO |
vivo |
R2-2204802 |
Correction on full configuration in TS 37.340 |
vivo |
R2-2204903 |
Clarifications on CPAC procedures |
NEC |
R2-2204957 |
Miscellaneous corrections to 37.340 CPAC |
Lenovo |
R2-2205164 |
Further consideration on CPAC/CHO coexistence |
ZTE Corporation, Sanechips |
R2-2205165 |
Clarification on CPAC/CHO coexistence |
ZTE Corporation, Sanechips |
R2-2205166 |
Clarification on CPAC/CHO coexistence |
ZTE Corporation, Sanechips |
R2-2205167 |
Clarification on CPAC/CHO coexistence |
ZTE Corporation, Sanechips |
R2-2205168 |
[E022] [V190] Discussion on conditional reconfiguration removal |
ZTE Corporation, Sanechips |
R2-2205169 |
[Z007] Correction to CondReconfigToAddModList |
ZTE Corporation, Sanechips |
R2-2205170 |
[Z003] Correction to CondReconfigurationToAddModList |
ZTE Corporation, Sanechips |
R2-2205171 |
[Z003][Z004] Discussion on applicable events for execution conditions |
ZTE Corporation, Sanechips |
R2-2205426 |
Discussion on the Remaining Issues of CPAC |
CATT |
R2-2205444 |
Miscellaneous CPAC corrections related to RIL E022, E023, E024 and E029 |
Ericsson |
R2-2205445 |
CPA and DAPS handover correction of RIL E050 |
Ericsson |
R2-2205446 |
Correction CR for MR-DC |
Ericsson |
R2-2205485 |
[E023] Introduction of UE variable for SN configured conditional Reconfigurations |
Samsung R&D Institute UK |
R2-2205524 |
Resolving incomplete CPAC issues |
Nokia, Nokia Shanghai Bell |
R2-2205525 |
Rel-17 CPAC corrections to 38.331 |
Nokia, Nokia Shanghai Bell |
R2-2205526 |
Rel-17 CPAC corrections to 36.331 |
Nokia, Nokia Shanghai Bell |
R2-2205527 |
Rel-17 CPAC corrections to 37.340 |
Nokia, Nokia Shanghai Bell |
R2-2205665 |
Introducing target cell ID to CPAC RRC |
Apple |
R2-2205831 |
Corrections to 37.340 for CPAC and CHO co-existence |
InterDigital |
R2-2205927 |
Corrections for CPAC |
Huawei, HiSilicon |
R2-2206116 |
Miscellaneous CPAC corrections related to RIL E022, E023, E024 and E029 |
Ericsson |
R2-2206139 |
[38.331 - H110] Applicable cell for a conditional reconfiguration |
Huawei, HiSilicon |
R2-2206140 |
[38.331 - H111] Handling of conditional configurations |
Huawei, HiSilicon |
R2-2206141 |
[38.331 - H067] Update of candidate target cell and configuration |
Huawei, HiSilicon |
R2-2206168 |
Report of [AT118-e][225][DCCA] RRC for CPAC (Ericsson) |
Ericsson |
R2-2206365 |
Report of [AT118-e][225][DCCA] RRC for CPAC (Ericsson) |
Ericsson |
6.2.4 |
Temporary RS for SCell activation |
|
R2-2204610 |
[RIL-O405]-38331CR Corrections on TRS based SCell activation |
OPPO |
R2-2204978 |
Leftover issues for TRS based SCell activation |
Samsung |
R2-2205059 |
Discussion on Temporary RS activation for fast SCell activation |
vivo |
R2-2205505 |
[E067][E068] TRS-based SCell activation |
Ericsson |
R2-2206369 |
Corrections for TRS-based SCell activation |
Samsung |
R2-2206370 |
Corrections for TRS-based SCell activation |
Samsung |
R2-2206679 |
Report of [AT118-e][226][DCCA] Corrections for TRS-based SCell activation (Samsung) |
Samsung |
R2-2206788 |
Corrections for TRS-based SCell activation |
Samsung |
R2-2206789 |
Corrections for TRS-based SCell activation |
Samsung |
6.2.5 |
UE capabilities |
|
R2-2205425 |
Discussion on UE Capability of CPAC |
CATT |
R2-2205934 |
Clarification on inter-SN CPC UE capability |
Huawei, HiSilicon |
6.3.1 |
Organizational |
|
R2-2204442 |
LS reply on RAN2 agreements for paging with service indication (S2-2201838 ; contact: vivo) |
SA2 |
R2-2204481 |
Reply LS on RAN2’s agreement for MUSIM gaps (R4-2207032; contact: vivo) |
RAN4 |
R2-2204542 |
Introduction of Multi-USIM devices to 36.304 |
China Telecom |
R2-2204892 |
Correction of NR RRC support for MUSIM |
vivo(Rapporteur) |
R2-2204893 |
Comments on MUSIM NR RRC Editorial class 0 issues |
vivo(Rapporteur) |
R2-2204894 |
RIL List comments on MUSIM NR RRC |
vivo(Rapporteur) |
R2-2205848 |
Corrections on MUSIM in LTE |
Samsung Electronics Co., Ltd |
R2-2205854 |
Discussion on Editorial class 0 issues and RIL issues for MUSIM in LTE |
Samsung Electronics Co., Ltd |
R2-2206169 |
Correction of NR RRC support for MUSIM |
vivo(Rapporteur) |
R2-2206170 |
Corrections on MUSIM in LTE |
Samsung |
R2-2206571 |
Summary of [AT118-e][230][MUSIM] NR RRC corrections for MUSIM (vivo) |
vivo |
R2-2206625 |
Correction of NR RRC support for MUSIM |
vivo(Rapporteur) |
R2-2206835 |
Correction of NR RRC support for MUSIM |
vivo |
R2-2206859 |
Introduction of Multi-USIM devices to 36.304 |
China Telecom |
6.3.2 |
Paging collision avoidance and paging with service indication |
|
R2-2204617 |
Paging cause handling for RRC-INACTIVE |
Nokia, Nokia Shanghai Bells |
R2-2204787 |
Corrections on Paging Cause for 38.331 [O800] |
OPPO |
R2-2204788 |
Corrections on Paging Cause for 36.331 [O806] |
OPPO |
R2-2204789 |
LS on NAS-AS interaction for paging cause |
OPPO |
R2-2205130 |
Interaction between NAS and AS for network switching |
ASUSTeK |
R2-2205172 |
Discussion on the cross layer indication for paging cause |
Huawei, HiSilicon |
R2-2205173 |
UE behaviour for NAS busy indication in RRC_INACTIVE |
Huawei, HiSilicon |
R2-2205216 |
Corrections to TS 38.300 spec for MUSIM |
Huawei, HiSilicon |
R2-2205336 |
Further Consideration on the Inactive State Busy Indication |
ZTE Corporation, Sanechips |
R2-2205542 |
Specifying UE behaviour for Paging cause for RAN based Paging |
Intel Corporation |
R2-2205762 |
Clarification on UE behavior for NAS-based busy indication in RRC_INACTIVE |
Samsung Electronics Co., Ltd |
R2-2206363 |
Report of [AT118-e][234][MUSIM] UE behavior for NAS-based busy indication in RRC_INACTIVE (Samsung) |
Samsung |
R2-2206574 |
Correction on UE behavior for NAS-based busy indication in RRC_INACTIVE |
Samsung |
R2-2206575 |
Correction on UE behavior for NAS-based busy indication in RRC_INACTIVE |
Samsung |
R2-2206837 |
LS on NAS busy indication in RRC_INACTIVE |
RAN2 |
6.3.3 |
NW switching for multi-SIM without leaving RRC_CONNECTED |
|
R2-2204614 |
Alternative ASN.1 for MUSIM Gap Configuration |
Nokia, Nokia Shanghai Bells |
R2-2204615 |
Alignment of text for MUSIM gap configuration |
Nokia, Nokia Shanghai Bells |
R2-2204618 |
On remaining issues for UAI related to MUSIM |
Nokia, Nokia Shanghai Bells |
R2-2204747 |
Remaining issues about UE indication on switching |
Spreadtrum Communications |
R2-2204895 |
Discussion on handling of MUSIM gaps |
vivo |
R2-2204896 |
Discussion on MUSIM gap priority |
vivo |
R2-2205042 |
Clarification on MAC behaviour during MUSIM gaps |
NEC |
R2-2205120 |
Stop using of MUSIM Gap requested to be released |
Sharp |
R2-2205197 |
Corrections to NW switching procedure without leaving RRC_CONNECTED |
Huawei, HiSilicon |
R2-2205312 |
[H083] Corrections to NR RRC for MUSIM |
Huawei, HiSilicon |
R2-2205322 |
Further consideration on the MUSIM gaps |
ZTE Corporation, Sanechips |
R2-2205652 |
Additional Issues related to MUSIM |
Apple |
R2-2205755 |
Mandatory values for Multi-USIM gap patterns |
Ericsson |
R2-2205758 |
Alignment between RAN2 and RAN4 Multi-USIM gap |
Ericsson |
R2-2205759 |
IE harmonization for MUSIM UAI and gap configuration |
Ericsson |
R2-2205763 |
[S676] Further discussion on handling of musim-GapConfig in RRC_INACTIVE |
Samsung Electronics Co., Ltd |
R2-2205765 |
[S676] Correction on handling of musim-GapConfig in RRC_INACTIVE_Opt 1 |
Samsung Electronics Co., Ltd |
R2-2205767 |
[S676] Correction on handling of musim-GapConfig in RRC_INACTIVE_Opt 2 |
Samsung Electronics Co., Ltd |
R2-2205772 |
[S677] Correction on the IE MUSIM-GapConfig in ASN.1 |
Samsung Electronics Co., Ltd |
R2-2205964 |
Configuration of MUSIM Gaps |
Qualcomm Incorporated |
R2-2206171 |
Report of [AT118-e][232][MUSIM] Corrections to MUSIM gap configuration aspects (Qualcomm) |
Qualcomm Inc. |
6.3.4 |
NW switching for multi-SIM with leaving RRC_CONNECTED |
|
R2-2205211 |
Further clarification on the wait timer for NW switching with leaving RRC_CONNECTED |
Huawei, HiSilicon |
R2-2205501 |
[L020] Correction for AS-based leaving when RAN paging in MUSIM |
LG Electronics Finland |
R2-2205729 |
Further clarification on the waiting timer for leaving connected state [Z294][O802] |
ZTE Corporation, Sanechips |
R2-2205757 |
Behaviour of wait timer |
Ericsson |
6.3.5 |
UE capabilities |
|
R2-2204616 |
Editorial corrections for UE capability |
Nokia, Nokia Shanghai Bells |
R2-2205547 |
Need for UE capability for Paging cause for RAN ID based paging |
Intel Corporation |
R2-2205756 |
Remaining aspects on UE capabilities for Multi-USIM and other issues |
Ericsson |
R2-2206182 |
Corrections to MUSIM UE capabilities |
Intel |
R2-2206183 |
Corrections to MUSIM UE capabilities |
Intel |
R2-2206362 |
Report of [AT118-e][233][MUSIM] UE capability corrections for MUSIM (Intel) |
Intel |
6.4.1.1 |
Organizational |
|
R2-2204430 |
LS on upper layers parameters for Rel-17 eIAB (R1-2202947; contact: Qualcomm) |
RAN1 |
R2-2204446 |
LS on upper layers parameters for Rel-17 eIAB (R1-2202737; contact: Qualcomm) |
RAN1 |
R2-2204460 |
Reply LS on range of power control parameters for eIAB (R1-2202877; contact: Samsung) |
RAN1 |
R2-2204461 |
LS on Rel-17 NR eIAB for TS 38.300 (R1-2202884; contact: Qualcomm) |
RAN1 |
R2-2205163 |
LS on eIAB MAC CEs |
Samsung R&D Institute UK |
R2-2206358 |
LS on eIAB MAC CEs |
RAN2 |
R2-2206469 |
Reply LS on eIAB MAC Ces (R1-2205293; contact: Qualcomm) |
RAN1 |
R2-2206757 |
LS on range of power control parameters for eIAB (R4-22010642; contact: Samsung) |
RAN4 |
R2-2206812 |
LS on upper layers parameters for Rel-17 eIAB (R1-2205644; contact: AT&T) |
RAN1 |
6.4.1.3 |
CR Rapporteur Resolutions |
|
R2-2204897 |
Miscilaneous Corrections to 37340 |
vivo(Rapporteur) |
R2-2205253 |
Miscellaneous CR for TS 38.340 |
Huawei, HiSilicon |
R2-2205268 |
CR to 38.321 on Integrated Access and Backhaul for NR Rel-17 |
Samsung R&D Institute UK |
R2-2205899 |
Miscellaneous Rapporteur RRC corrections to IAB |
Ericsson |
R2-2206346 |
Summary of [Pre118-e][009][eIAB] 38331 CR and rapporteur resolutions (Ericsson) |
Ericsson |
R2-2206347 |
Miscellaneous Rapporteur RRC corrections to IAB |
Ericsson |
R2-2206530 |
Report of [AT118-e][066][eIAB] BAP |
Huawei, HiSilicon |
R2-2206545 |
[AT118-e][067][eIAB] 38300 – Summary of PH1 discussion |
Qualcomm (Rapporteur) |
R2-2206570 |
Summary of [AT118-e][064][eIAB] RRC (Ericsson) |
Ericsson |
R2-2206572 |
Summary of [AT118-e][068][eIAB] 37340 (vivo) |
vivo (Rapporteur) |
R2-2206573 |
Miscellaneous Corrections to 37.340 |
vivo |
R2-2206581 |
Miscellaneous corrections to 38.321 on Integrated Access and Backhaul for NR Rel-17 |
Samsung |
R2-2206582 |
Summary of discussion [AT118-e][065][eIAB] MAC (Samsung) |
Samsung |
R2-2206583 |
Summary of discussion [AT118-e][063][eIAB] Support of requested MAC CEs (Ericsson, Samsung) |
Samsung, Ericsson |
R2-2206682 |
Various corrections to IAB enhancements |
Qualcomm (Rapporteur) |
R2-2206684 |
Miscellaneous CR for TS 38.340 |
Huawei, HiSilicon |
R2-2206786 |
Miscellaneous Rapporteur RRC corrections to IAB |
Ericsson |
R2-2206790 |
Miscellaneous corrections to 38.321 on Integrated Access and Backhaul for NR Rel-17 |
Samsung, LG Electronics |
R2-2206791 |
CR to 38.321 on Integrated Access and Backhaul for NR Rel-17 |
Samsung |
R2-2206869 |
Miscellaneous Corrections to 37.340 |
vivo |
6.4.3 |
Open Issues |
|
R2-2205139 |
Slot index signalling options and way forward |
Samsung R&D Institute UK |
R2-2205288 |
Discussion on new MAC CEs in the exception sheet |
LG Electronics Inc. |
R2-2205895 |
Addressing the new Rel.17 IAB MAC CEs |
Ericsson |
R2-2205896 |
Corrections to IAB MAC CEs design in MAC specification |
Ericsson |
R2-2205897 |
Corrections to IAB MAC CEs design in RRC specification |
Ericsson |
R2-2206787 |
Introducing IAB MAC CE Configurations in RRC |
Ericsson |
R2-2206877 |
Introducing IAB MAC CE Configurations in RRC |
Ericsson |
6.4.4 |
Corrections |
|
R2-2204790 |
Miscellaneous corrections on IAB in 37.340 |
ZTE, Sanechips |
R2-2204794 |
Miscellaneous IAB Corrections in 38.300 |
ZTE, Sanechips |
R2-2204898 |
Corrections to 38300 |
vivo |
R2-2204977 |
Correction on BH RLF detection indication |
Lenovo (Beijing) Ltd |
R2-2205147 |
Miscellaneous eIAB corrections to 38.300 |
Samsung R&D Institute UK |
R2-2205256 |
Corrections on rerouting in TS 38.300 for eIAB |
Huawei, HiSilicon |
R2-2205257 |
Corrections on F1-C traffic transfer for eIAB in TS 37.340 |
Huawei, HiSilicon |
R2-2205900 |
Corrections to IAB MR-DC procedures |
Ericsson |
R2-2205902 |
Miscellaneous corrections to IAB stage-2 specification |
Ericsson |
6.4.4.1 |
Control Plane |
|
R2-2204792 |
Miscellaneous corrections on IAB in 38.331 |
ZTE, Sanechips |
R2-2204911 |
[F008] CR for 38.331 on deriving the topology of IP address configuration |
Fujitsu |
R2-2205160 |
Miscellaneous eIAB corrections to 38.331 |
Samsung R&D Institute UK |
R2-2205500 |
[S726][S727] Handling of IP address requestreport for IAB MR-DC scenarios |
Samsung R&D Institute UK |
R2-2205521 |
Inclusion of IABOtherInformation message in RRC Transfer procedure |
Samsung R&D Institute UK |
R2-2205898 |
Corrections to IABOtherInformation [E144] |
Ericsson |
R2-2206094 |
[H044] [H045] Corrections on the AvailabilityCombination for eIAB |
Huawei, HiSilicon |
R2-2206095 |
[H041] Corrections on the BAP entity release for eIAB |
Huawei, HiSilicon |
6.4.4.2 |
User Plane |
|
R2-2204793 |
Miscellaneous IAB Corrections on BAP in 38.340 |
ZTE, Sanechips |
R2-2204881 |
Local congestion-based re-routing at divergence point of DL paths |
Nokia, Nokia Shanghai Bell |
R2-2204899 |
Corrections to 38340 |
vivo |
R2-2204900 |
Corrections to 38321 |
vivo |
R2-2204901 |
On Padding BSR Procedure of IAB |
vivo |
R2-2204912 |
Miscellaneous corrections to TS 38.340 |
Fujitsu |
R2-2204913 |
SCG deactivation impact on NR eIAB |
Fujitsu |
R2-2205041 |
Clarification on extended BSR of eIAB for TS 38.300 |
NEC |
R2-2205254 |
Corrections on the handling of unknown, unforeseen, and erroneous protocol data for header rewriting case in TS 38.340 |
Huawei, HiSilicon |
R2-2205255 |
Corrections on the Extended BSR MAC CE and case-6 timing mode for eIAB |
Huawei, HiSilicon |
R2-2205287 |
Correction on extended BSR procedure and RIL [S733] |
LG Electronics Inc. |
R2-2206040 |
Miscellaneous corrections to 38.340 for eIAB |
Qualcomm Incorporated |
6.4.5 |
UE capabilities |
|
R2-2204791 |
Correction on IAB-MT capability of header rewriting based re-routing |
ZTE, Sanechips |
R2-2205258 |
Corrections on the bapHeaderRewriting-Routing and lcg-ExtensionIAB for eIAB |
Huawei, HiSilicon |
R2-2206534 |
[AT118-e][069][eIAB] UE caps (Intel) |
Intel Corporation |
R2-2206535 |
Draft 38.306 CR for UE capabilities for Rel-17 eIAB |
Intel Corporation |
6.5.1 |
Organizational |
|
R2-2204416 |
RE: LS on Time Synchronization |
IEEE 1588 WG |
R2-2204480 |
Reply LS on propagation delay compensation (R4-2207021; contact: Huawei) |
RAN4 |
R2-2204519 |
Reply Time Synchronization support in 3GPP (S2-2203229; contact: Ericsson) |
SA2 |
R2-2205506 |
Summary of [Pre118-e][502][IIoT URLLC] 38331 CR and rapporteur resolutions (Ericsson) |
Ericsson |
R2-2205507 |
Correction for enhanced IIoT&URLLC support for NR |
Ericsson |
R2-2205683 |
CR for procedure level alignment of UL skipping |
Apple |
R2-2205710 |
Correction for Enhanced NR IIoT and URLLC in 38.321 |
Samsung |
R2-2206117 |
RE: LS on Time Synchronization |
IEEE 1588 WG |
R2-2206351 |
Correction for enhanced IIoT&URLLC support for NR |
Ericsson |
R2-2206685 |
Corrections for IIoT on simultaneous PUCCH and PUSCH transmission |
Nokia (rapporteur), CATT |
R2-2206698 |
Correction for Enhanced NR IIoT and URLLC in 38.321 |
Samsung, CATT, OPPO, Ericsson |
R2-2206806 |
LS on Rel-17 URLLC/IIoT RRC parameter updates (R1-2205507; contact: Nokia) |
RAN1 |
R2-2206864 |
Correction for enhanced IIoT&URLLC support for NR |
Ericsson |
6.5.2 |
Control Plane |
|
R2-2204758 |
[O500,O501] Clarification on the usage of sib9Fallback |
OPPO |
R2-2204866 |
Remaining issue of PDC calculation based on measurements for single pair of RSs |
Huawei, HiSilicon |
R2-2204867 |
Resolution of remaining issue of PDC calculation |
Huawei, HiSilicon |
R2-2204868 |
Miscellenous corrections to RRC spec for IIoT [H701] [H702] [H703] |
Huawei, HiSilicon |
R2-2205508 |
Multi-TB scheduling in UCE |
Ericsson |
R2-2205509 |
On unresolved RIL issues |
Ericsson |
R2-2205732 |
Consideration on meeting very low latency requirement in TDD |
ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
R2-2205734 |
[DRAFT] Reply LS on RAN feedback for low latency |
ZTE Corporation, Sanechips |
R2-2206006 |
Discussion on ta-PDC and sib9Fallback for IIoT |
ZTE Corporation, Sanechips |
R2-2206223 |
Summary of [AT118-e][505][IIoT] CP open issues and CR 38.331 (Ericsson) |
Ericsson |
R2-2206350 |
Summary of "[AT118-e][505][IIoT] CP open issues and CR 38.331 (Ericsson)" |
Ericsson |
6.5.3 |
User Plane |
|
R2-2204665 |
Correction on Simultaneous PUCCH/PUSCH Transmission |
CATT |
R2-2204666 |
Corrections on the description of simultaneous PUCCH/PUSCH transmission |
CATT |
R2-2204759 |
Correction on the simultaneous PUCCH PUSCH transmission |
OPPO, Samsung |
R2-2204760 |
Open issues on the termination of the CGT |
OPPO |
R2-2205019 |
Correction on duplication activation for survival time state entry |
Nokia, Nokia Shanghai Bell |
R2-2205020 |
Correction on duplication activation with UL retransmission grant reception |
Nokia, Nokia Shanghai Bell |
R2-2205021 |
Corrections on HARQ feedback deferral |
Nokia, Nokia Shanghai Bell |
R2-2205460 |
Clarification on the SPS HARQ deferral |
Xiaomi Communications |
R2-2205510 |
correction for PDCP duplication with survivalTimeSupport |
Ericsson, Samsung |
R2-2205680 |
Impact of Rel-17 PHY prioritization on MAC |
Apple |
R2-2205681 |
Draft CR for impact of Rel-17 PHY prioritization on MAC |
Apple |
R2-2205711 |
Correction of HARQ RTT Timer Handling |
Samsung |
R2-2206028 |
Clarification on the SPS HARQ deferral |
Xiaomi Communications, Samsung |
R2-2206222 |
Summary of IIOT/URLLC User Plane |
Samsung |
R2-2206467 |
Summary of Offline 506: IIOT UP Open Issues |
Samsung |
6.6.1 |
Organizational |
|
R2-2204431 |
NAS's trigger for resume for SDT (C1-221891; contact: OPPO) |
CT1 |
R2-2204445 |
Reply LS on the physical layer aspects of small data transmission (R1-2202656; contact: ZTE) |
RAN1 |
R2-2204455 |
Reply LS on Security of Small data transmission (S3-220463; contact: Intel) |
SA3 |
R2-2205552 |
[Draft] LS on the L1 related agreements for SDT |
ZTE Corporation (rapporteur) |
R2-2205834 |
Corrections on SDT |
Nokia, Nokia Shanghai Bell |
R2-2206475 |
LS on CG period values for small data transmission (R1-2205347; contact: ZTE) |
RAN1 |
R2-2206497 |
LS on transferring SDT related information in case of SDT with UE context relocation (R3-223880; contact: CATT) |
RAN3 |
R2-2206622 |
Reply LS on transferring SDT related information in case of SDT with UE context relocation |
RAN2 |
R2-2206742 |
LS on transferring SDT configuration and SRS positioning Inactive configuration from DU to CU (R3-223955; contact: Google) |
RAN3 |
R2-2206761 |
Reply LS on TA validation for CG-SDT (R4-2211122; contact: ZTE) |
RAN4 |
R2-2206798 |
Reply LS on Small Data Transmission (C1-224149; contact: Apple) |
CT1 |
R2-2206819 |
Corrections on SDT |
Nokia, Nokia Shanghai Bell, Samsung, OPPO |
R2-2206828 |
Reply LS on the L1 related agreements for SDT |
RAN2 |
6.6.2 |
User plane common aspects |
|
R2-2204533 |
Corrections to RA Trigger during the ongoing CG-SDT procedure |
Samsung Electronics Co., Ltd |
R2-2204534 |
Corrections to UL TA handling upon Contention resolution during CG-SDT |
Samsung Electronics Co., Ltd |
R2-2204836 |
[V537]-[V540] L1 Parameter Correction for CG-SDT |
vivo |
R2-2204973 |
Consideration on UP Remaining Issues of SDT |
CATT |
R2-2204983 |
Editor's correction to MAC spec for Small Data Transmission |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
R2-2205045 |
Remaining user plane issues of SDT |
NEC |
R2-2205152 |
Consideration on Stored RSRP for CG-SDT TA validation |
CATT |
R2-2205214 |
Remaining UP open issues for SDT |
Lenovo |
R2-2205217 |
TP for RNAU with CG Type 1 and PDCP control PDU transmission |
Lenovo |
R2-2205243 |
Remaining issues of SDT UP aspects |
Qualcomm Incorporated |
R2-2205270 |
Discussion on remaining UP issues of SDT |
OPPO |
R2-2205271 |
Correction for RACH triggered events |
OPPO |
R2-2205289 |
Correction to TA validation for CG-SDT |
Huawei, HiSilicon |
R2-2205343 |
Collison of PUCCH and PUSCH for SDT |
Sony |
R2-2205550 |
User plane open issues for SDT |
ZTE Corporation, Sanechips |
R2-2205588 |
CG timer use in CG-SDT procedure |
Ericsson |
R2-2205597 |
Validation of CG-SDT occasions |
Ericsson |
R2-2205835 |
MAC procedure issues |
Nokia, Nokia Shanghai Bell |
R2-2205836 |
UP procedure issues |
Nokia, Nokia Shanghai Bell |
R2-2205940 |
Stage-2 corrections for Small Data Transmission |
Huawei, HiSilicon |
R2-2206066 |
Editor's correction to MAC spec for Small Data Transmission |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
R2-2206261 |
Summary for [Post118-e][604] 38.321 Positioning CR (Huawei) |
Email discussion Rapporteur (Huawei, HiSilicon) |
R2-2206341 |
Summary of the AI 6.6.2 for SDT User Plane |
Huawei, HiSilicon |
R2-2206342 |
Email discussion for AI 6.6.2 for SDT User Plane |
Huawei, HiSilicon |
R2-2206343 |
Correction to MAC spec for Small Data Transmission |
Huawei, HiSilicon, Samsung, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
R2-2206711 |
SSB selection for CG-SDT |
Huawei, HiSIicon, Nokia, Nokia Shanghai Bell |
R2-2206712 |
Summary for [POST 118-e][502][Sdata] UP open issues and CR to 38.321 (Huawei) |
Huawei, HiSilicon |
R2-2206862 |
Correction to MAC spec for Small Data Transmission |
Huawei, HiSilicon, Samsung, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
6.6.3 |
Control plane common aspects |
|
R2-2204532 |
Corrections for paging-emergency SIBs-RRCRelease duriing SDT |
Samsung Electronics Co., Ltd |
R2-2204835 |
[V534][V536] RRC Procedural Corrections for SDT |
vivo |
R2-2204972 |
[C092] Further considerations upon reception of RRC Release |
CATT |
R2-2204984 |
[H549] Correction for restoring the logical channel configuration from UE context |
Huawei, HiSilicon |
R2-2204985 |
[H559] Correction for transitition to RRC_CONNECTED for SDT |
Huawei, HiSilicon |
R2-2205043 |
UAC upon non-SDT data arrival |
NEC |
R2-2205044 |
[W002][W005] Control plane issues of SDT |
NEC |
R2-2205221 |
TP for the PDCP control PDU transmission and UAC with CG Type 1 |
Lenovo |
R2-2205244 |
Remaining issues of SDT CP aspects |
Qualcomm Incorporated |
R2-2205354 |
Discussion on the NAS aspects of Small Data Transmission |
Huawei, HiSilicon |
R2-2205355 |
[H562] Correction for internode message for SDT |
Huawei, HiSilicon |
R2-2205459 |
RIL(X304) Clarification on the cell configured for CG-SDT |
Xiaomi Communications |
R2-2205548 |
Control plane open issues for SDT |
ZTE Corporation, Sanechips |
R2-2205549 |
SDT RRC Corrections |
ZTE Corporation (rapporteur) |
R2-2205551 |
RRC RIL issue summary for SDT |
ZTE Corporation (rapporteur) |
R2-2205590 |
Actions on receiving indication of failure to perform SDT procedure |
Ericsson |
R2-2205668 |
SDT related RIL Issues (RIL A000, A001, A002, A003, A004, A005,A007) |
Apple |
R2-2205669 |
SDT TAT related RIL Issue (RIL A019) |
Apple |
R2-2205670 |
UAC operation during the CG-SDT procedure (RIL A006) |
Apple |
R2-2205788 |
SDT CP procedure issues |
Nokia, Nokia Shanghai Bell |
R2-2205818 |
[I503] Reception of RRCRelease for SDT |
Intel Corporation |
R2-2205819 |
[I511] T319a maximum range |
Intel Corporation, Sony |
R2-2205820 |
[I505] Search space for pdcch-Config of CG-SDT |
Intel Corporation |
R2-2205821 |
[I508] Introduction of SDT in resume procedure |
Intel Corporation |
R2-2205822 |
[506] Signaling allowed during SDT |
Intel Corporation |
R2-2205823 |
[I507] Clarify the reference to “part of the UE configuration” in the procedural text |
Intel Corporation |
R2-2205824 |
[I512] [I010] SRS Positioning configuration provided for SDT |
Intel Corporation |
R2-2205825 |
[I513] Clarification of SRB1 configuration used for SDT |
Intel Corporation |
R2-2206017 |
Introduction of Small Data Transmission into 38.304 |
vivo |
R2-2206065 |
Alignment of DRX for Paging with RRC for SDT |
vivo |
R2-2206125 |
Discussion on Need S versus Need R for some SDT fields (RIL: H551, H556) |
Huawei, HiSilicon |
R2-2206224 |
Alignment of DRX for Paging with RRC for SDT |
vivo |
R2-2206335 |
Actions on receiving indication of failure to perform SDT procedure |
Ericsson |
R2-2206481 |
[AT118-e][501][Sdata] CP Open issues and CR to 38.331 (ZTE) - Report |
ZTE |
R2-2206483 |
SDT RRC Corrections |
ZTE Corporation (rapporteur) |
R2-2206485 |
UE capability on maximum value of T319a for Rel-17 SDT WI |
Intel Corporation |
R2-2206486 |
UE capability on maximum value of T319a for Rel-17 SDT WI |
Intel Corporation |
R2-2206826 |
[POST118-e][501][Sdata] CP Open issues and CR to 38.331 (ZTE) - summary |
ZTE corporation (rapporteur) |
R2-2206827 |
SDT corrections |
ZTE Corporation (rapporteur) |
6.7.1 |
Organizational |
|
R2-2204436 |
LS reply on support of RAN sharing and discovery signalling (S2-2201296; contact: Huawei) |
SA2 |
R2-2204440 |
Reply LS on discovery and data associated to different L2 IDs (S2-2201298; contact: vivo) |
SA2 |
R2-2204447 |
LS on the SDU type used over user plane for NR PC5 reference point (C1-221835; contact: ZTE) |
CT1 |
R2-2204584 |
38.300 CR Correction for SL Relay |
MediaTek Inc. |
R2-2204632 |
Correction on SRAP for L2 U2N Relay |
OPPO |
R2-2204633 |
Discussion on CT1 LS on SDU type (C1-221835) |
OPPO |
R2-2204771 |
Issues on the SDU Type Used over User Plane for NR PC5 Reference Point |
CATT |
R2-2204772 |
Correciton on PDCP for SL relay |
CATT |
R2-2204798 |
Discussion on the SDU type used over user plane for NR PC5 reference point |
ZTE, Sanechips |
R2-2204799 |
Draft reply LS on SDU type used over user plane for NR PC5 reference point |
ZTE, Sanechips |
R2-2205607 |
Correction on RLC for SL relay |
Samsung |
R2-2205608 |
Correction on PDCP for SL relay |
Samsung |
R2-2205648 |
Correction for sidelink relay in MAC |
Apple |
R2-2205880 |
38.306 CR for sidelink relay UE capabilities |
Qualcomm Incorporated |
R2-2205986 |
Miscellaneous RRC CR for SL relay |
Huawei, HiSilicon |
R2-2206231 |
Miscellaneous RRC CR for SL relay |
Huawei, HiSilicon |
R2-2206232 |
Correction on stage 2 for sidelink relay |
MediaTek Inc. |
R2-2206233 |
Miscellaneous correction on SL relay |
Ericsson |
R2-2206234 |
38.306 CR for sidelink relay UE capabilities |
Qualcomm Incorporated |
R2-2206235 |
Correction for sidelink relay in MAC |
Apple |
R2-2206236 |
Correction on RLC for SL relay |
Samsung |
R2-2206237 |
Correction on PDCP for SL relay |
Samsung |
R2-2206238 |
Correction on SRAP for L2 UE-to-Network Relay |
OPPO |
R2-2206382 |
Summary of [AT118-e][615][Relay] 38321 relay CR (Apple) |
Apple |
R2-2206465 |
Summary of [AT118-e][619][Relay] LS on SDU type in PDCP (ZTE) |
ZTE |
R2-2206466 |
Reply LS on SDU type used over user plane for NR PC5 reference point |
ZTE, Sanechips |
R2-2206588 |
[AT118-e][613][Relay] Discussion on 38304 |
Ericsson |
R2-2206589 |
Miscellaneous correction on SL relay |
Ericsson |
R2-2206597 |
Reply LS on SDU type used over user plane for NR PC5 reference point |
RAN2 |
R2-2206823 |
Miscellaneous corrections for NR SL Relay |
Huawei, HiSilicon |
6.7.2.1 |
Control plane procedures |
|
R2-2204550 |
Discussion on paging information management for a remote UE |
SHARP Corporation |
R2-2204551 |
Discussion on cell change of remote UE due to relay UE's cell change |
SHARP Corporation |
R2-2204585 |
General SIB forwarding for Remote UE [M119][H629] |
MediaTek Inc. |
R2-2204586 |
Positioning SIB forwarding for Remote UE [M119][H629] |
MediaTek Inc. |
R2-2204634 |
Correction on [O006, O007, O008, O010, O011, O054, O900] |
OPPO |
R2-2204674 |
[E083][H593] Two copies of a same SIB and related remote UE behaviour |
vivo |
R2-2204676 |
OOC concept for remote UE |
vivo |
R2-2204764 |
[C121] Necessity of Releasing the Paging Request of Remote UE via SidelinkUEInformationNR |
CATT |
R2-2204765 |
[C122]Conditions of RemoteUEInformationSidelink Transmission |
CATT |
R2-2204766 |
Discussion on the LCIDs of SL-SCH for Uu Logical Channels of Remote UE |
CATT |
R2-2204886 |
Discussion on SI forwarding |
NEC Corporation |
R2-2204959 |
[B104] TP on stop condition of T300 |
Lenovo |
R2-2204960 |
[B105] TP on setup request procedure |
Lenovo |
R2-2204961 |
[B106] TP on re-establishment procedure |
Lenovo |
R2-2204989 |
Discussion on inter layer interaction for NR sidelink relay |
OPPO |
R2-2204991 |
Correction to support L3 U2N Relay |
OPPO |
R2-2205014 |
[H629] Correction for SI request for posSIB for SL remote UE |
Huawei, HiSilicon |
R2-2205064 |
Discussion on remote UE’s SIB(s) acquisition and paging monitoring |
ZTE, Sanechips |
R2-2205065 |
Correction on remote UE’s SIB(s) acquisition and paging monitoring |
ZTE, Sanechips |
R2-2205113 |
Cause value for Relay UE (38.331 running CR) |
LG Electronics France |
R2-2205115 |
remaining issues for control plane procedure for relay operation |
LG Electronics France |
R2-2205131 |
Connection establishment and resume failure occurrence to a L2 U2N Remote UE |
ASUSTeK |
R2-2205132 |
Associating two sidelink RLC bearer configurations for bi-directional sidelink RLC bearer to support L2 U2N Relay |
ASUSTeK |
R2-2205319 |
Discussion on how to support posSIB(s) forwarding |
Xiaomi |
R2-2205321 |
[X208] Discussion on remote UE’s on-demand SI in CONNECTED |
Xiaomi |
R2-2205496 |
Correction on cause value in sidelink relay |
Nokia, Nokia Shanghai Bell |
R2-2205609 |
Clarification of SI acquisition for RRC_IDLE/RRC_INACTIVE Remote UE (RIL#: E084, H593) |
Samsung |
R2-2205695 |
[B100] SL Timer Broadcast in SIB1 |
Lenovo |
R2-2205699 |
[B212] RRC Connected Remote UE cannot acquire SIB1 |
Lenovo |
R2-2205856 |
Correction for RRC Reestablishment in Sidelink relay |
Nokia, Nokia Shanghai Bell |
R2-2205905 |
Draft CR on Corrections on Paging Reception by the Relay UE |
InterDigital |
R2-2205906 |
[U455] Draft CR on Corrections to Paging DRX Cycle |
InterDigital |
R2-2205907 |
[U456][U473] Draft CR on Corrections to Trigger Conditions of RemoteUEInformationSidelink |
InterDigital |
R2-2205908 |
[U465] Draft CR on Corrections to Relay UE Uu SI Request |
InterDigital |
R2-2205909 |
[U482] Draft CR on Corrections to NotificationMessageSidelink |
InterDigital |
R2-2205991 |
Clarification on relay and remote UE behavior during failure handling |
Huawei, HiSilicon |
R2-2206042 |
Discussion on [O090] |
OPPO |
R2-2206242 |
Summary report of [AT118-e][620][Relay] System information issues (Qualcomm) |
Qualcomm Incorporated |
R2-2206253 |
Summary of [AT118-e][632][Relay] Cell change for remote UE (InterDigital) |
InterDigital |
R2-2206339 |
Summary of [Pre118-e][608][Relay] Summary of AI 6.7.2.1 on CP (Lenovo) |
Lenovo |
R2-2206399 |
Summary of [AT118-e][632][Relay] Cell change for remote UE (InterDigital) |
InterDigital |
6.7.2.2 |
Service continuity |
|
R2-2204635 |
Correction on [O009, o017, O020, O022-O025] |
OPPO |
R2-2204795 |
Miscellaneous corrections for NR SL Relay in 38.300 |
ZTE, Sanechips |
R2-2204990 |
Correction to support IDLE INACTIVE relay UE |
OPPO |
R2-2205093 |
38.331 CR for SL relay events |
Samsung |
R2-2205320 |
[X200] Discussion on path swith failure upon target relay UE Pcell change |
Xiaomi |
R2-2205339 |
Service continuity open issues in L2 NR sidelink relay |
Sony |
R2-2205375 |
On the entry and leave conditions for path switch in SL relay |
Nokia, Nokia Shanghai Bell |
R2-2205633 |
Discussion on how remote UE gets its local ID in direct-to-indirect
path switch when target relay UE is in IDLE/INACTIVE state |
Apple |
R2-2205987 |
Clarification on Uu threshold handling when configured with measurements of L2 U2N Relay Ues |
Huawei, HiSilicon |
R2-2206053 |
Summary of 6.7.2.2 service continuity (Xiaomi) |
Xiaomi |
6.7.2.3 |
Adaptation layer design |
|
R2-2204796 |
Correction on BEARER ID determination |
ZTE, Sanechips |
R2-2204797 |
Correction on the DL bearer mapping |
ZTE, Sanechips |
R2-2205133 |
Corrections on SRAP PDU handling and ID field determination |
ASUSTeK |
R2-2205431 |
Correction on the handling of unknown, unforeseen, and erroneous protocol data and other miscellaneous in SRAP |
Huawei, HiSilicon |
6.7.2.4 |
QoS |
|
R2-2204993 |
Correction for sequential rule of destination index |
OPPO |
6.7.2.5 |
Discovery and re/selection |
|
R2-2204564 |
[V353][Z652] Discussion and corrections on CBR measurements for NR SL discovery |
vivo |
R2-2204587 |
Relay selection requirement conflict [M112][v208] |
MediaTek Inc. |
R2-2204636 |
Correction on [O042, O047-O049, O058-O060] |
OPPO |
R2-2204675 |
[V410][O058] Dedicated pool for discovery reception |
vivo |
R2-2204767 |
Discussion on Resource Pool Selection for Discovery Message |
CATT |
R2-2204768 |
Correlation on Resource Pool Selection for Discovery Message |
CATT |
R2-2204769 |
Introduction of LCID for discovery message |
CATT |
R2-2204992 |
Correction to support non-relay discovery |
OPPO |
R2-2205063 |
Correction on the Sidelink discovery transmission |
ZTE, Sanechips |
R2-2205114 |
Reduction of some parts of selection of logical channels in SL Relay (38.321 running CR) |
LG Electronics France |
R2-2205345 |
Sidelink discovery operation - monitoring and transmission |
Beijing Xiaomi Mobile Software |
R2-2205356 |
Discussion on MAC functionality for discovery |
Huawei, HiSilicon |
R2-2205357 |
Assisting L2 Remote UE to correctly evaluate threshold condition |
Huawei, HiSilicon |
R2-2205610 |
Correction on SL discovery and UL prioritization |
Samsung |
R2-2205963 |
Correction on Groupcast transmission mode support for sidelink discovery |
Qualcomm Incorporated |
R2-2206056 |
Summary of AI 6.7.2.5 on Discovery and (re)selection |
vivo |
R2-2206243 |
Initial comments on discovery and (re)selection of AI 6.7.2.5 summary |
vivo (Rapporteur) |
R2-2206381 |
Summary of [640] Cast type for discovery (OPPO) |
OPPO |
R2-2206391 |
LS on Cast Type for Discovery message |
RAN2 |
6.7.2.6 |
UE capabilities |
|
R2-2204637 |
Correction on UE capability for discovery BC list (38.331) |
OPPO |
R2-2204638 |
Correction on UE capability for discovery BC list (38.306) |
OPPO |
R2-2204770 |
Further discussion on UE capability |
CATT |
R2-2205988 |
Clarification on supported BC of Uu and sidelink discovery |
Huawei, HiSilicon |
R2-2206394 |
Correction on UE capability for discovery BC list (38.331) |
OPPO |
6.7.2.7 |
ASN.1 issues |
|
R2-2204677 |
[V202][V205] PC5 RRC connection establishment and release trigger |
vivo |
R2-2204678 |
[V207][V208] L2 U2N Remote UE RRC re-establishment procedure |
vivo |
R2-2204679 |
[V213] Discussion on timers related issues |
vivo |
R2-2204680 |
[Z684] Max destination index and resource allocation impact |
vivo |
R2-2204958 |
[B103] TP for initiation condition of notification message |
Lenovo |
R2-2204962 |
[B107] TP on unsuitable relay during re-establishment |
Lenovo |
R2-2204994 |
Correction on the definition of suitable relay UE |
OPPO |
R2-2205066 |
Correction on PC5 RLC channel configuration |
ZTE, Sanechips |
R2-2205092 |
38.331 CR for allow and exclude list on eventX1 (RIL#:S776) |
Samsung |
R2-2205186 |
Correction on RIL issue E132 |
Ericsson |
R2-2205187 |
Correction on RIL issues (E041, E043, E044 and E045) |
Ericsson |
R2-2205228 |
Correction on RIL issues (E041, E043, E044 and E045) |
Ericsson |
R2-2205634 |
Discussion on whether UE dedicated PC5 configuration can be configured
in RRCReestablishment message (RIL A308, A906) |
Apple |
R2-2205635 |
Discussion on definition of U2N remote UE (RIL A304, A305, A307, A311) |
Apple |
R2-2205645 |
[A903] Discussion on SIB12 configuration for relay support |
Apple |
R2-2205646 |
[A309] Discussion on relay UE notification upon Uu RLF |
Apple |
R2-2205685 |
[B207][B208] Correction in NR sidelink U2N Remote UE operation |
Lenovo Mobile Com. Technology |
R2-2205690 |
[B209][B10][B211] Various corrections for Paging monitoring and System Information acquisition |
Lenovo |
R2-2205773 |
[E080] Correction on UE states and state transitions for SL relay |
Ericsson |
R2-2205774 |
[E082] Correction on receiving short message by remote UE |
Ericsson |
R2-2205775 |
[E084][E085] Correction on on-demand SIB for SL relay |
Ericsson |
R2-2205776 |
[E086] Correction on cell barring for SL relay |
Ericsson |
R2-2205777 |
[E087] Correction on paging reception by the remote UE |
Ericsson |
R2-2205778 |
[E090] Correction on reconfigurationWithSync handling during path switch |
Ericsson |
R2-2205779 |
[E093] Correction on new UE timers for remote UE |
Ericsson |
R2-2205780 |
[E104][E112] Correction on handling on timer T420 |
Ericsson |
R2-2205826 |
[M116, A906, I012, I046] SL information in RRC Setup and Reestablishment messages |
Intel Corporation |
R2-2205962 |
RIL#Q539 - Correction on Groupcast and unicast transmission modes support for sidelink discovery |
Qualcomm Incorporated |
R2-2206072 |
[H810][M106][O075][O076][B207][B208] On term of OoC, suitable cell, serving cell |
Huawei, HiSilicon |
R2-2206073 |
[H808][X200] Identification of target Relay UE‘s serving cell change |
Huawei, HiSilicon |
R2-2206074 |
[H811][N005]Change SetupRelease to optional for L2 remote configuration in RRCSetup/Resume/Reestablishment |
Huawei, HiSilicon |
R2-2206075 |
[H812][O94][I012] SRB1 SRAP configuration and defaut RLC configuration at PC5 hop |
Huawei, HiSilicon |
R2-2206076 |
[H809][A304, A305, A307, A311] Clarification on the meaning of acting as/capable of/is a relay UE/remote UE |
Huawei, HiSilicon |
R2-2206077 |
Draft CR for SL relay class1/2 RIL issues (Output of Pre118-e #602) |
Huawei, HiSilicon |
R2-2206078 |
Report of Pre118-e #602 |
Huawei, HiSilicon |
R2-2206254 |
Report of [AT118-e][633][Relay] Remaining ASN.1 review issues (Huawei) |
Huawei, HiSilicon |
6.7.3 |
Other |
|
R2-2204773 |
Miscellaneous Corrections on SL Relay |
CATT |
R2-2204800 |
TP to introduce Rel-17 sidelink relay and discovery in TR 37.985 |
ZTE, Sanechips |
R2-2205432 |
Corrections on stage2 specification for sidelink relay |
Huawei, HiSilicon |
R2-2205611 |
Support of non-IP PDU type in PDCP protocol |
Samsung |
R2-2205781 |
Misc correction on 38.300 for SL relay |
Ericsson |
R2-2205989 |
Clarification on NR sidelink relay related configuration |
Huawei, HiSilicon |
R2-2206239 |
Draft CR to introduce Rel-17 sidelink relay and discovery for TR 37.985 |
ZTE, Sanechips |
R2-2206240 |
(LS from [618]) |
ZTE |
R2-2206519 |
Summary of [AT118-e][618][Relay] 37985 relay TP (ZTE) |
ZTE |
6.8.1 |
Organizational |
|
R2-2204526 |
Reply LS on Slice list and priority information for cell reselection (S2-2203597; contact: ZTE) |
SA2 |
R2-2205082 |
Discussion on RIL list for RAN slicing |
Huawei, HiSilicon |
R2-2205083 |
Discussion on Editorial issues for RAN slicing |
Huawei, HiSilicon |
R2-2205084 |
Corrections to TS 38.331 for RAN slicing |
Huawei, HiSilicon |
R2-2205491 |
Updates for RAN Slicing from RAN2#118 |
Nokia, Nokia Shanghai Bell |
R2-2206172 |
Corrections to TS 38.331 for RAN slicing |
Huawei, HiSilicon (Rapporteur) |
R2-2206173 |
Report of [AT118-e][240][Slicing] Finalizing RRC for RAN slicing (Huawei) |
Huawei (Rapporteur) |
R2-2206184 |
Report from [AT118-e][241][Slicing] Finalizing Stage-2 for RAN slicing (Nokia) |
Nokia (Rapporteur) |
R2-2206800 |
Reply LS on Slice list and priority information for cell reselection (C1-224295; contact: OPPO) |
CT1 |
6.8.2 |
Cell reselection |
|
R2-2204554 |
Considerations on the slice info configured by RRCRelease for cell reselection |
Beijing Xiaomi Software Tech |
R2-2204571 |
Slice based cell reselection priorities handling for equal priority slice groups |
Beijing Xiaomi Software Tech |
R2-2204583 |
Corrections on the slice based cell reselection priorites |
Beijing Xiaomi Software Tech |
R2-2204590 |
Corrections on slice based cell reselection configured by RRCRelease |
Beijing Xiaomi Software Tech |
R2-2204603 |
Discussion on slice group handling |
NTT DOCOMO INC. |
R2-2204746 |
Discussion on remaining issues for slice based cell reselection |
Spreadtrum Communications |
R2-2204761 |
Clarification on reselection priorities for slice-based cell reselection |
OPPO, Xiaomi |
R2-2204762 |
Open issues on slice-specific cell reselection |
OPPO |
R2-2205032 |
Discussion on open issues for slice based cell reselection |
CMCC |
R2-2205077 |
Corrections on TS 38.300 for RAN Slicing |
Huawei, HiSilicon |
R2-2205078 |
Corrections on TS 38.304 for RAN Slicing |
Huawei, HiSilicon |
R2-2205079 |
Discussion on Slice Information |
Huawei, HiSilicon |
R2-2205080 |
Discussion on UE behaviours during slice group specific cell reselection |
Huawei, HiSilicon |
R2-2205124 |
Equal priority cases for Slice Specific Cell Reselection |
Kyocera |
R2-2205151 |
Clarification on slice-based cell reselection based on SA2 conclusion |
Qualcomm Incorporated |
R2-2205157 |
Clarification on slice-based cell re-selection based on SA2 conclusion |
Qualcomm Incorporated |
R2-2205464 |
Discussion on the impacts of LS from SA2 on RAN2 |
CATT |
R2-2205465 |
Consideration on issues of RRCRelease |
CATT |
R2-2205466 |
The impact of re-sorting on RRM requirement |
CATT |
R2-2205467 |
Draft CR to TS 38.304 on the remaining RRC Open issues for slicing |
CATT |
R2-2205468 |
[C154] Create a new IE for SliceGroupID |
CATT |
R2-2205492 |
Clarifications on slice groups and other corrections |
Nokia, Nokia Shanghai Bell |
R2-2205493 |
Clarifications on slice groups and other corrections |
Nokia, Nokia Shanghai Bell |
R2-2205494 |
Clarifications on slice groups and other corrections [N031, N032] |
Nokia, Nokia Shanghai Bell |
R2-2205495 |
Considerations on reselection information priorities |
Nokia, Nokia Shanghai Bell |
R2-2205543 |
Remaining open issue on interaction with legacy dedicated priority and broadcast slice based cell reselection |
Intel Corporation |
R2-2205568 |
[Z325] Discussion on the FreqPriorityListNRSlicing |
ZTE corporation, Sanechips |
R2-2205569 |
Discussion on the slice group and slice priority |
ZTE corporation, Sanechips |
R2-2205570 |
draft LS on slice group |
ZTE corporation, Sanechips |
R2-2205576 |
Remaining open points on slice group and slice priority |
Samsung R&D Institute UK |
R2-2205587 |
Text Proposal for corrections for TS 38.304 on RAN slicing |
Samsung R&D Institute UK |
R2-2205615 |
[B204][B205][B206] Some RRC corrections |
Lenovo |
R2-2205616 |
Resolving FFS on slice Information in RRC Release and SIB |
Samsung |
R2-2205619 |
[S254] Correction for FreqPriorityNRSlicing |
Samsung |
R2-2205662 |
Discussion on SA2 LS on RAN Slicing |
Apple |
R2-2205663 |
Discussion on leftover issues in RAN slicing |
Apple |
R2-2205693 |
Remaining FFS points in RAN Slicing |
Lenovo |
R2-2205737 |
Information Provided in RRCRelease (partially relevant to RIL#H502) |
NEC Telecom MODUS Ltd. |
R2-2205739 |
CR to 38.304 Clarification on slice-specific cell reselection |
NEC Telecom MODUS Ltd. |
R2-2205972 |
[E140] Freq list in SIB16 for slicing |
Ericsson |
R2-2205973 |
RAN Slicing enhancements in shared RAN |
Ericsson |
R2-2205974 |
Discussion and way forward on Slice based Cell re-selection |
Ericsson |
R2-2205975 |
Resolving open issues |
Ericsson |
R2-2205976 |
Resolving open issues |
Ericsson |
R2-2206097 |
[H505] Slice cell list in RRCRelease message |
Huawei, HiSilicon |
R2-2206174 |
CR to 38.304 Clarification on slice-specific cell reselection |
NEC Telecom MODUS Ltd. |
R2-2206185 |
Report of [AT118-e][242][Slicing] Finalizing IDLE mode for RAN slicing (NEC) |
NEC |
R2-2206336 |
Comparison of slice group solutions |
Ericsson |
R2-2206373 |
CR to 38.304 Clarification on slice-specific cell reselection |
NEC Telecom MODUS Ltd. |
R2-2206376 |
38.304 CR Corrections on slice-based cell reselection |
NEC |
R2-2206845 |
38.304 CR Corrections on slice-based cell reselection |
NEC |
6.8.3 |
RACH |
|
R2-2204763 |
Open issues on slice-specific RACH |
OPPO |
R2-2204785 |
Consideration on slice specific RACH and another issue |
Purple Mountain Laboratories |
R2-2204873 |
Correction to RA initialization for slicing |
Nokia, Nokia Shanghai Bell |
R2-2205081 |
Discussion on slice group specific RACH |
Huawei, HiSilicon |
R2-2205365 |
[X802 X804] Considerations on the slice based RA prioritization parameters configuration |
Beijing Xiaomi Software Tech |
R2-2205612 |
Clarification on RACH configuration for slice |
Samsung |
R2-2206175 |
Corrections to 38.321 on RAN slicing |
Samsung |
R2-2206186 |
[AT118-e][243][Slicing] Finalizing MAC for slice-specific RACH |
Samsung |
R2-2206834 |
Correction on MAC specification for RAN slicing |
Samsung |
6.8.4 |
UE capabilities |
|
R2-2205546 |
Remaining open issues on UE Capability for slice based cell reselection |
Intel Corporation |
R2-2205977 |
UE Capabilities for Slice-based Cell re-selection and RA |
Ericsson |
R2-2206366 |
Corrections to RAN slicing UE capabilities |
Intel Corporation |
6.9.1.1 |
Organizational |
|
R2-2204466 |
LS reply on PDCCH skipping (R1-2202905; contact: vivo) |
RAN1 |
R2-2204484 |
ReplyLS to RAN2 on RLM/BFD relaxation for ePowSav (R4-2207087; contact: vivo) |
RAN4 |
R2-2204499 |
Reply LS on paging subgrouping and PEI (R3-222874; contact: ZTE) |
RAN3 |
R2-2204522 |
Reply LS out on PEI and UE Subgrouping (S2-2203252; contact: Qualcomm) |
SA2 |
R2-2204602 |
37.340 Draft CR for ePowSav |
Xiaomi Communications,Nokia, Nokia Shanghai Bell,ZTE Corporation, Sanechips |
R2-2204803 |
[V149] Discussion on reply LS on signaling for RLM BFD relaxation |
vivo |
R2-2206632 |
Reply LS on PEI and UE Subgrouping (R3-224004; contact: ZTE) |
RAN3 |
R2-2206675 |
Reply LS to RAN4 on RLM BFD relaxation |
RAN2 |
R2-2206818 |
Introduction of UE power saving enhancements In 37.340 |
Xiaomi, Nokia, Nokia Shanghai Bell,ZTE Corporation, Sanechips |
R2-2206878 |
Introduction of UE power saving enhancements In 37.340 |
Xiaomi, Nokia, Nokia Shanghai Bell,ZTE Corporation, Sanechips |
6.9.1.3 |
CR Rapporteur Resolutions |
|
R2-2204804 |
Miscellaneous CR on TS 38.304 for ePowSav |
vivo |
R2-2205022 |
Stage 2 correction on power saving |
Nokia, Nokia Shanghai Bell |
R2-2205023 |
38304 corrections on power saving |
Nokia, Nokia Shanghai Bell |
R2-2205353 |
Corrections for UE power saving enhancements In 38.300 |
Huawei, HiSilicon |
R2-2206054 |
Report of [Pre118-e][008][ePowSav] 38331 CR and rapporteur |
CATT |
R2-2206055 |
ePowSav corrections for 38.331 |
CATT |
R2-2206493 |
Report of [AT118-e][071][ePowSav] RRC (CATT) |
CATT |
R2-2206494 |
ePowSav corrections for 38.331 |
CATT |
R2-2206598 |
Report of [AT118-e][071][ePowSav] RRC (CATT) – Phase 2 |
CATT |
R2-2206842 |
Corrections to UE power saving enhancements In 38.300 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
R2-2206844 |
Corrections on TS 38.304 for ePowSav |
Vivo (Rapporteur) |
R2-2206853 |
ePowSav corrections for 38.331 |
CATT (rapporteur) |
R2-2206882 |
Corrections to UE power saving enhancements In 38.300 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
6.9.3.1 |
PEI and Subgrouping |
|
R2-2204536 |
PEI Monitoring in last cell |
Samsung Electronics Co., Ltd |
R2-2204537 |
[S1000] PEI Monitoring in Redcap Specific BWP |
Samsung Electronics Co., Ltd |
R2-2204538 |
Selective Monitoring of PDCCH monitoring occasions of PEI |
Samsung Electronics Co., Ltd |
R2-2204539 |
Corrections for PEI Monitoring |
Samsung Electronics Co., Ltd |
R2-2204722 |
[O356] correction on signalling for indication of not supporting subgrouping |
OPPO |
R2-2204730 |
Discussion on PEI indication determination in RRC INACTIVE |
OPPO |
R2-2204786 |
[X107][O357]Discussing on the misalignment of RAN1_RAN2 on PEI without subgrouping |
Xiaomi Communications |
R2-2204805 |
Discussion on remaining issues on paging subgrouping and PEI |
vivo |
R2-2205198 |
Draft LS on PEI without subgrouping |
Xiaomi Communications |
R2-2205212 |
Introduction of PEI-RNTI |
MediaTek Inc., Huawei |
R2-2206044 |
PEI and subgrouping |
Ericsson |
R2-2206458 |
Report of [AT118-e][072][ePowSav] PEI and Subgrouping (Mediatek) |
MediaTek Inc. |
R2-2206775 |
Report of [Post118-e][072][ePowSav] PEI and Subgrouping (MediaTek) |
MediaTek Inc. |
6.9.3.2 |
RLM and BFD relaxation |
|
R2-2204721 |
[O375] correction on RLM/BFD relaxation |
OPPO |
R2-2204731 |
Discussion on UAI for relaxation state for RLM and BFD |
OPPO |
R2-2204745 |
Discussion on UE relaxation status reporting |
Spreadtrum Communications |
R2-2204806 |
[V135-V139, V141-143] Remaining issues on configuration for RLM/BFD relaxation |
vivo |
R2-2204807 |
Discussion on prohibit timer for RLM/BFD relaxation reporting |
vivo |
R2-2204888 |
Discussion on UE reporting for RLM BFD relaxation |
NEC Europe Ltd |
R2-2204974 |
UE assistance information for RLM/BFD relaxation |
CATT |
R2-2204975 |
[V137]Low mobility criterion in NR-DC |
CATT |
R2-2205095 |
[M001][N103][V138] Open Issues for RLM/BFD Relaxation |
MediaTek Inc. |
R2-2205213 |
Discussion on remaining issues on prohibit timer of UAI |
Xiaomi Communications |
R2-2205219 |
[X118]Correction on the UAI reporting for RLM_BFD relaxation |
Xiaomi Communications |
R2-2205286 |
[J005] Clarification on the state report of RLM/BFD relaxation |
Sharp |
R2-2205348 |
Remaining issues on the prohibit timer for RLM/BFD relaxation |
Huawei, HiSilicon |
R2-2205349 |
Correction for the prohibit timer for RLM/BFD relaxation |
Huawei, HiSilicon |
R2-2205350 |
Correction for the criteria configuration for RLM and BFD |
Huawei, HiSilicon |
R2-2205351 |
Discussion on the fulfilment condition for low mobility criterion |
Huawei, HiSilicon |
R2-2205408 |
Considerations On [RIL]s For BFR&RLM Relaxation |
ZTE Corporation,Sanechips |
R2-2205409 |
Considerations On the RLM&BFD Relaxation Indication to NW |
ZTE Corporation,Sanechips |
R2-2205410 |
CR in 38.331 For indication of RLM&BFD relaxation to NW |
ZTE Corporation,Sanechips |
R2-2205412 |
Further Considerations On the RLM&BFD relaxation in DC Mode |
ZTE Corporation,Sanechips |
R2-2205575 |
Further considerations on RLM BFD relaxation |
CMCC |
R2-2205591 |
RLM/BFD Relaxation Reporting |
Interdigital, Inc. |
R2-2205653 |
Enhanced NR UE Power Save - RLM/BFD Measurement Relaxation Indication |
Apple |
R2-2206045 |
Relaxed RLM and BFD measurements |
Ericsson |
R2-2206532 |
Report of [AT118-e][073][ePowSav] RLM and BFD relaxation (vivo) |
vivo |
6.9.3.3 |
Other |
|
R2-2204535 |
PDCCH skipping in RRC_CONNECTED and SR |
Samsung Electronics Co., Ltd |
R2-2204732 |
Discussion on PDCCH skipping |
OPPO |
R2-2204808 |
Discussion on issues for PDCCH skipping |
vivo |
R2-2204809 |
Discussion on TRS availability when SI change |
vivo |
R2-2204908 |
TRS/CSI-RS configuration in RRC_CONNECTED |
DENSO CORPORATION |
R2-2205024 |
Remaining issues on PDCCH adaptation |
Nokia, Nokia Shanghai Bell |
R2-2205025 |
Correction on PDCCH adaptation IEs |
Nokia, Nokia Shanghai Bell |
R2-2205352 |
Discussion on PDCCH skipping while SR is pending |
Huawei, HiSilicon |
R2-2205411 |
Considerations On the Left Issue For PDCCH Skipping |
ZTE Corporation,Sanechips |
R2-2205435 |
Discussion on PDCCH skipping while SR is pending |
LG Electronics Deutschland |
R2-2205751 |
PDCCH monitoring adaptation |
Ericsson |
R2-2205795 |
[Draft] Reply LS to RAN1 on PDCCH skipping |
vivo |
R2-2206031 |
Discussion on PDCCH skipping with pending SR |
Qualcomm Incorporated |
R2-2206046 |
TRS and CSI-RS exposure |
Ericsson |
R2-2206487 |
Report of [AT118-e][074][ePowSav] PDCCH skipping (Samsung) |
Samsung Electronics Co., Ltd |
6.9.4 |
UE capabilities |
|
R2-2205752 |
UE capabilities for UE power saving |
Ericsson |
6.10.1.1 |
LS in |
|
R2-2204450 |
LS on introducing the list of PLMNs not allowed to operate at the present UE location (C1-222096; contact: CMCC) |
CT1 |
R2-2204468 |
Reply LS on NTN-specific SIB (R1-2202843; contact: Huawei) |
RAN1 |
R2-2204470 |
Reply LS to RAN2 on NR NTN Neighbour Cell and Satellite Information (R1-2202873; contact: Thales) |
RAN1 |
R2-2204496 |
Reply LS on UE location during initial access in NTN (R3-222861; contact: Thales |
RAN3 |
R2-2204520 |
Reply LS on RAN Initiated Release due to out-of-PLMN area condition (S2-2203242; contact: Samsung) |
SA2 |
R2-2205027 |
Discussion on CT1 LS about NR satellite RAT type in UE NAS |
CMCC |
R2-2205028 |
[DRAFT] Reply LS on NR satellite RAT type in UE NAS |
CMCC |
R2-2205158 |
Impact on Cell selection/re-selection by the new PLMN list from CT1 |
CMCC |
R2-2205159 |
draft Reply LS on introducing the list of PLMNs not allowed to operate at the present UE location |
CMCC |
R2-2206041 |
Discussion on ambiguity of cell-specific K_offset |
Huawei, HiSilicon |
R2-2206206 |
Report of [AT118][114][NTN] reply LSs to CT1 (CMCC) |
CMCC |
R2-2206416 |
Reply LS on system information |
RAN2 |
R2-2206507 |
Summary of [AT118-e][112][NTN] Stage-2 CR (Thales) |
Thales |
R2-2206663 |
TP for 38.304 on PLMNs not allowed |
CMCC |
R2-2206664 |
Reply LS on NR satellite RAT type in UE NAS |
RAN2 |
R2-2206755 |
Reply LS on measurement gap enhancements for NTN (R4-2210611; contact: Intel) |
RAN4 |
R2-2206813 |
LS reply on Reply LS on NTN specific User Consent and UE location in connected mode in NTN (S3-221268; contact: Ericsson) |
SA3 |
6.10.1.2 |
Rapporteur CRs |
|
R2-2204627 |
Support of UE location in Non-Terrestrial Networks |
THALES |
R2-2204628 |
SAN for NTN based NG-RAN |
THALES |
R2-2205448 |
NTN ASN1 RIL list |
Ericsson |
R2-2205463 |
Correction for NR NTN WI |
Ericsson |
R2-2206088 |
Summary of NTN RIL resolutions pre118 |
Ericsson |
R2-2206202 |
Support of UE location in Non-Terrestrial Networks |
THALES |
R2-2206500 |
NTN corrections to 38.304 |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
R2-2206502 |
Correction for NR NTN WI |
Ericsson |
R2-2206503 |
Corrections to Release-17 NR Non-Terrestrial Networks (NTN) |
InterDigital |
R2-2206509 |
Corrections to stage 2 for NR NTN |
THALES |
R2-2206613 |
Draft 38.306 CR for NR NTN capablitie |
Intel Corporation |
R2-2206614 |
Draft 38.331 CR for NR NTN capablities |
Intel Corporation |
R2-2206661 |
Support of UE location in Non-Terrestrial Networks |
THALES |
R2-2206866 |
Corrections to Release-17 NR Non-Terrestrial Networks (NTN) |
InterDigital |
6.10.2.1 |
Known Corrections |
|
R2-2204556 |
Corrections on the TAR triggers based on RRC procedures in NR NTN |
vivo |
R2-2204557 |
On corrections on random access procedure in NR NTN |
vivo |
R2-2204558 |
On corrections to DRX procedure and TA reporting procedure in TS 38.321 |
vivo |
R2-2204656 |
TA report trigger in NTN |
Qualcomm Incorporated |
R2-2204657 |
Handling the loss of UL synchronization |
Qualcomm Incorporated |
R2-2204733 |
Discussion on ra-ContentionResolutionTimer in NTN |
OPPO |
R2-2204734 |
left issue on TA report triggered SR |
OPPO |
R2-2204735 |
Further discussion on validity timer impacts in NTN |
OPPO |
R2-2204748 |
MAC operations about the validity timer expiry |
Spreadtrum Communications |
R2-2205134 |
Corrections for TA report |
ASUSTeK |
R2-2205135 |
Discussion on TP for blind Msg3 retransmission |
ASUSTeK |
R2-2205232 |
UE Behavior upon Validity Timer Expiry |
CATT |
R2-2205240 |
Discussion on remaining issues |
LG Electronics Inc. |
R2-2205358 |
Clarification on contention Resolution timer behavior |
ZTE Corporation, Sanechips |
R2-2205359 |
Consideration on RTT timer extension implementation |
ZTE Corporation, Sanechips |
R2-2205403 |
Remaining issues related to NTN validity timer |
Xiaomi |
R2-2205477 |
Discussion on Contention Resolution timer expiry |
Huawei, HiSilicon |
R2-2205478 |
Further consideration on TA report MAC CE |
Huawei, HiSilicon |
R2-2205596 |
Further consideration on TA report |
ZTE Corporation, Sanechips |
R2-2205694 |
Discussion on MAC open issues |
Samsung Research America |
R2-2205702 |
Consideration on validity timer related issues |
ZTE Corporation, Sanechips |
R2-2205720 |
Discussion on user plane known issues for NR NTN |
Nokia, Nokia Shanghai Bell |
R2-2205721 |
CR for Contention Resolution failure, SR and TA MAC CE report |
Nokia, Nokia Shanghai Bell |
R2-2205954 |
HARQ RTT timer extention |
InterDigital |
R2-2205955 |
TA Reporting during Random Access |
InterDigital |
R2-2205956 |
UE behaviour upon validity timer expiry |
InterDigital |
R2-2205994 |
Known NR NTN user plane issues |
Ericsson |
R2-2206194 |
Report of [AT118-e][104][NTN] UP corrections: Phase 1 |
InterDigital |
R2-2206207 |
Report of [AT118-e][104][NTN] UP corrections: Phase 2 |
InterDigital |
R2-2206212 |
Report of [AT118-e][104][NTN] UP RILs and detailed issues |
InterDigital |
R2-2206352 |
Summary of [Pre118-e][104][NTN] UP corrections |
InterDigital |
R2-2206612 |
Report of [AT118-e][104][NTN] UP Corrections: Phase 4 |
InterDigital |
6.10.2.2 |
Other |
|
R2-2204559 |
Miscellaneous corrections on TS 38.321 for NR NTN |
vivo |
R2-2205231 |
The Modification of TA Reporting Triggering Condition |
CATT |
R2-2205340 |
CG enhancements in NTN |
Sony |
R2-2205360 |
Discussion on co-existence of Msg3 repetition and NTN |
ZTE Corporation, Sanechips |
R2-2205722 |
On other user plane issues for NR NTN |
Nokia, Nokia Shanghai Bell |
R2-2205995 |
Other NR NTN user plane issues |
Ericsson |
R2-2205999 |
Correction to NR NTN epoch time definition |
Sequans Communications |
6.10.3.1.1 |
Known Corrections |
|
R2-2204563 |
Remaining issue on access barring for NTN |
vivo |
R2-2204592 |
Discussion on remaining issue of NTN idel/inactive mode |
Transsion Holdings |
R2-2204658 |
TN NTN barring mechanism |
Qualcomm Incorporated |
R2-2204709 |
Discussion on location-based cell reselection in NTN |
OPPO |
R2-2204714 |
Discussion on neighbour cell's epoch time and Koffset's ambiguity issue |
OPPO |
R2-2204749 |
Discussion on SIB X acquiring procedure |
Spreadtrum Communications |
R2-2205029 |
Discussion on cell reselection |
CMCC |
R2-2205094 |
Remaining issue on idle/inactive mode |
ITL |
R2-2205110 |
Remaining issues on idle/inactive mode and RRC aspects |
LG Electronics France |
R2-2205234 |
Discussion on the parameters influencing SI modification procedure |
CATT |
R2-2205236 |
Further Discussion on Cell Reselection |
CATT |
R2-2205237 |
Discussion on the access barring in NTN |
CATT |
R2-2205301 |
Discussion on SIB19 processing and updating |
Huawei, HiSilicon |
R2-2205302 |
Discussion on access barring |
Huawei, HiSilicon |
R2-2205303 |
[H803] Discussion on on-demand SIB for NTN |
Huawei, HiSilicon |
R2-2205371 |
Discussion on remaining issues on RRC idle mode |
Xiaomi |
R2-2205405 |
Further Discussion on Cell Reselection |
CATT |
R2-2205528 |
Resolving open NTN issues for IDLE mode |
Nokia, Nokia Shanghai Bell |
R2-2205530 |
Assistance information for UE-based SMTC adjustment in idle and inactive mode |
Nokia, Nokia Shanghai Bell |
R2-2205531 |
Rel-17 NTN corrections to 38.304 |
Nokia, Nokia Shanghai Bell |
R2-2205533 |
Cell reselection with distance threshold |
Samsung |
R2-2205571 |
Left over issues in idle and inactive mode in NTN |
ZTE corporation, Sanechips |
R2-2205573 |
Reporting UE location to the Network in NTN |
Samsung R&D Institute UK |
R2-2205650 |
Cell-specific K_offset ambiguity |
Apple |
R2-2205651 |
Epoch time and validity timer expiry |
Apple |
R2-2205691 |
Adding SMTC4 for idle/inactive state |
Apple |
R2-2205696 |
Open issues on acquiring SIB |
Samsung Research America |
R2-2205700 |
RILs on epoch time |
Samsung Research America |
R2-2205740 |
Distance based cell reselection |
NEC Telecom MODUS Ltd. |
R2-2205753 |
NTN Access barring and UE behaviour |
NEC Telecom MODUS Ltd. |
R2-2205754 |
RIL# H803/TS38.300: Clarification on SIB19 Provisioning |
NEC Telecom MODUS Ltd. |
R2-2205865 |
NR NTN idle mode issues |
Ericsson |
R2-2206029 |
UE based SMTC adjustment |
LG Electronics Inc. |
R2-2206035 |
Remaining issues on idle/inactive mode and RRC aspects |
LG Electronics France |
R2-2206197 |
Report of [AT118-e][107][NTN] System information (Huawei) |
Huawei, HiSilicon |
R2-2206201 |
Report of [AT117-e][111][NTN] Idle mode |
ZTE corporation,Sanechips |
R2-2206208 |
Report of [AT118-e][107][NTN] System information (Huawei) |
Huawei, HiSilicon |
R2-2206413 |
Report of [AT118-e][107][NTN] System information (Huawei) |
Huawei, HiSilicon |
6.10.3.1.2 |
Other |
|
R2-2205471 |
RIL V313 and PLMN aspects |
Ericsson |
6.10.3.2.1 |
Known Corrections |
|
R2-2204560 |
[V320] CGI reporting in R17 NR NTN |
vivo |
R2-2204561 |
[V319][V305][V310] Remaining issues on signalling design and corresponding procedures for neighbour cell assistance information in NR NTN |
vivo |
R2-2204562 |
[V313] On the issue for RAN area code configuration in NR NTN |
vivo |
R2-2204659 |
Time-based CHO after T2 |
Qualcomm Incorporated |
R2-2204660 |
Assistance information for IDLE mode measurements in NTN |
Qualcomm Incorporated |
R2-2204663 |
SMTC and MG configuration |
Qualcomm Incorporated |
R2-2204713 |
Discussion on implementing HARQ RTT timer extension |
OPPO |
R2-2204715 |
Discussion on assistance information for IDLE mode and CONNECTED mode measurement |
OPPO |
R2-2204717 |
[O358] NTN RRC correction |
OPPO |
R2-2204718 |
[O355] NTN RRC correction |
OPPO |
R2-2204719 |
[O354] NTN RRC correction |
OPPO |
R2-2204720 |
[O350] NTN RRC correction |
OPPO |
R2-2204750 |
Acquiring the ephemeris of neighbour cell |
Spreadtrum Communications |
R2-2204963 |
Remaining issues of provisioning neighbor cell satellite information |
Lenovo |
R2-2204964 |
Remaining details of UE assistance reporting and CHO |
Lenovo |
R2-2205225 |
Remaining issues of NTN CHO |
Xiaomi Communications |
R2-2205230 |
Correction on HARQ RTT Timer extension in TS38.331 |
CATT |
R2-2205233 |
Discussion on Neighbor Cell Satellite Information |
CATT |
R2-2205235 |
Further Discussion on CHO |
CATT |
R2-2205304 |
Discussion on SMTC and gaps |
Huawei, HiSilicon |
R2-2205305 |
Discussion on time/location based mobility |
Huawei, HiSilicon |
R2-2205341 |
CHO configuration after T2 expiry |
Sony |
R2-2205342 |
Event triggered location reporting in NTN |
Sony |
R2-2205372 |
Assistance information for neighbour cell measurement |
Xiaomi |
R2-2205401 |
Further details for coarse location report for NR NTN |
Xiaomi |
R2-2205402 |
[RIL]X601/O350/M403: Introducing NTN validity timer in RRC |
Xiaomi |
R2-2205404 |
Discussion on Neighbor Cell Satellite Information |
CATT |
R2-2205436 |
RIL: M404, V318, Z550 CHO configuration discarded or retained after T2 |
Ericsson |
R2-2205438 |
SMTC for RRC_IDLE and RRC_INACTIVE state in NR NTN |
Ericsson |
R2-2205529 |
Resolving open NTN issues for CONNECTED mode |
Nokia, Nokia Shanghai Bell |
R2-2205574 |
Coarse location format |
Ericsson |
R2-2205589 |
SMTC Offset and Change Rate |
Google Inc. |
R2-2205697 |
Discussion on CHO open issues |
Samsung Research America |
R2-2205698 |
Discussion on SMTC open issues |
Samsung Research America |
R2-2205957 |
Time-based CHO configuration after T2 |
InterDigital |
R2-2205958 |
Configuration of Timing Advance reporting in TS 38.331 |
InterDigital |
R2-2206030 |
Propagation delay difference reporting |
LG Electronics Inc. |
R2-2206057 |
[RIL]X601/O350/M403: Introducing NTN validity timer in RRC |
Xiaomi, MediaTek |
R2-2206090 |
[O350][X601][L014][L015][M403]Correction on maintenance of validity timer |
Huawei, HiSilicon |
R2-2206191 |
[AT118-e][101][NTN] RRC CR (Ericsson) |
Ericsson |
R2-2206196 |
Report from [AT118-e][106][NTN] CP issues (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2206209 |
[AT118-e][101][NTN] RRC CR (Ericsson) |
Ericsson |
R2-2206210 |
Report from [AT118-e][106][NTN] CP issues – second round (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2206501 |
Report from [AT118-e][106][NTN] CP issues – third round (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2206505 |
Report from [AT118-e][106][NTN] CP issues – fourth round (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2206506 |
Summary of [AT118-e][119][NTN] Coarse UE location info (Thales) |
Thales |
R2-2206508 |
[AT118-e][101][NTN] RRC CR (Ericsson) |
Ericsson |
R2-2206617 |
[offline-120] UE assistance for SMTC |
OPPO |
R2-2206619 |
TP (TS 38.331) about coarse location report based on RRM |
Thales (moderator) |
6.10.3.2.2 |
Other |
|
R2-2204661 |
Reporting SMTC issue in measurement results |
Qualcomm Incorporated |
R2-2204716 |
Discussion on connected mode measurement start |
OPPO |
R2-2205030 |
Discussion on SMTC and MG configuration for connected mode in NTN |
CMCC |
R2-2205224 |
[X704] Correction for Event D1 |
Xiaomi Communications |
R2-2205226 |
Discussion on performing measurements for NTN CHO |
Xiaomi Communications |
R2-2205592 |
Essential system information missing for NTN |
Interdigital, Inc. |
R2-2205621 |
[L011] TP on MR triggered by event D1 |
LG Electronics France |
R2-2205623 |
[L014] TP on Ul sync assist info validity |
LG Electronics France |
R2-2206036 |
Discussion on SMTC and MG configuration for connected mode in NTN |
CMCC |
R2-2206068 |
[H800] Discussion on condEventD1 |
Huawei, HiSilicon |
R2-2206069 |
[H801] Corrections on eventD1 |
Huawei, HiSilicon |
R2-2206112 |
[H024] Adding a conditional presence to ntn-UlSyncValidityDuration |
Huawei, HiSilicon |
6.10.4.1 |
Known remaining issues |
|
R2-2204662 |
NTN UE capability signalling |
Qualcomm Incorporated |
R2-2204843 |
Discussion on remaining issues on NTN UE capabilities |
Intel Corporation, THALES |
R2-2205306 |
Discussion on UE capabilities for NTN |
Huawei, HiSilicon |
R2-2205572 |
On NTN capabilities |
Ericsson |
R2-2205593 |
NTN-only UE |
Interdigital, Inc. |
R2-2205701 |
Open issues on UE capabilities |
Samsung Research America |
R2-2206198 |
Report of email discussion [AT118-e][108][NTN] UE capabilities (Intel) |
Intel Corporation |
R2-2206211 |
Report of email discussion [AT118-e][108][NTN] UE capabilities (Intel) |
Intel Corporation |
6.10.4.2 |
Other |
|
R2-2204842 |
Clarification on TA reporting UE capability |
Intel Corporation |
6.11.1 |
Organizational |
|
R2-2204420 |
Reply LS on positioning issues needing further input (R1-2202849; contact: CATT) |
RAN1 |
R2-2204424 |
Reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance (R1-2202912; contact: CATT) |
RAN1 |
R2-2204425 |
LS on multiple measurement instances (R1-2202922; contact: CATT) |
RAN1 |
R2-2204441 |
Response LS on determination of location estimates in local co-ordinates (S2-2201545; contact: Ericsson) |
SA2 |
R2-2204464 |
LS on frequency information of SRS for positioning resources (R1-2202847; contact: CATT) |
RAN1 |
R2-2204477 |
LS on lower Rx beam sweeping factor for latency improvement (R4-2206980; contact: Intel) |
RAN4 |
R2-2204478 |
LS on the UE/TRP TEG framework (R4-2206998; contact: CATT) |
RAN4 |
R2-2204491 |
Questions concerning the implementation of RAN1 agreements in NRPPa (R3-222721; contact: Ericsson) |
RAN3 |
R2-2204508 |
Reply LS on latency improvement for PRS measurement with MG (R4-2207088; contact: Huawei) |
RAN4 |
R2-2204521 |
Reply LS on Positioning in RRC_INACTIVE State (S2-2203250; contact: Huawei) |
SA2 |
R2-2204684 |
[Draft] Reply LS on the response of the positioning issues from RAN1(R1-2202849; contact: CATT) |
CATT |
R2-2204685 |
Reply LS on the reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance (R1-2202912; contact: CATT) |
CATT |
R2-2204686 |
Reply LS on multiple measurement instances (R1-2202922; contact: CATT) |
CATT |
R2-2204687 |
Reply LS on frequency information of SRS for positioning resources (R1-2202847; contact: CATT) |
CATT |
R2-2204688 |
Reply LS on the UE/TRP TEG framework (R4-2206998; contact: CATT) |
CATT |
R2-2204930 |
Open issues on TS38.305 |
Intel Corporation |
R2-2204931 |
38.305 CR for Positioning WI |
Intel Corporation |
R2-2204934 |
Known corrections/issues for the correction phase on Rel-17 positioning WI |
Intel Corporation |
R2-2204995 |
Corrections on stage 2 for path RSRP |
Huawei, HiSilicon |
R2-2205828 |
Summary of LPP Updates and Open Issues |
Qualcomm Incorporated |
R2-2205829 |
LPP Updates |
Qualcomm Incorporated |
R2-2205859 |
Correction based upon Positioning RILs |
Ericsson |
R2-2206150 |
Response LS to RTCM SC134 on GNSS integrity (RTCM; contact: ESA) |
RTCM |
R2-2206244 |
38.305 CR for Positioning WI |
Intel Corporation |
R2-2206245 |
36.305 CR for Positioning WI |
Intel Corporation |
R2-2206246 |
Correction based upon Positioning RILs |
Ericsson |
R2-2206247 |
LPP Updates |
Qualcomm Incorporated |
R2-2206248 |
Correction on MAC spec for posEnh |
Huawei, HiSilicon |
R2-2206249 |
Reply LS on the UE/TRP TEG framework |
RAN2 |
R2-2206251 |
Response LS on DL-AoD signalling load |
RAN2 |
R2-2206264 |
[Post118-e][603][POS] 37.355 positioning CR |
Qualcomm Incorporated |
R2-2206383 |
[AT118-e][623][POS] 38331 positioning CR (Ericsson) |
Ericsson |
R2-2206385 |
[AT118-e][626][POS] LS on TEG framework (CATT) |
CATT |
R2-2206386 |
Report of [AT118-e][622][POS] 38305 positioning CR (Intel) |
Intel Corporation |
R2-2206392 |
Summary for [AT118-e][625][POS] 38321 positioning CR (Huawei) |
Huawei, HiSilicon |
R2-2206555 |
Reply LS on lower Rx beam sweeping factor for latency improvement (R1-2205450; contact: Huawei) |
RAN1 |
R2-2206593 |
Summary of [AT118-e][624][POS] 37355 positioning CR (Qualcomm) |
Qualcomm Incorporated |
R2-2206752 |
Further reply LS on condition for PRS measurement outside the MG (R4-2210601; contact: Huawei) |
RAN4 |
R2-2206753 |
LS on Tx TEG framework (R4-2210603; contact: CATT) |
RAN4 |
R2-2206754 |
LS on switching time for SRS transmission outside initial UL BWP in RRC_INACTIVE (R4-2210604; contact: Huawei) |
RAN4 |
R2-2206801 |
Reply LS on the UE/TRP TEG framework (R1-2205382; contact: CATT) |
RAN1 |
R2-2206802 |
LS on updates of RRC parameters for Rel-17 positioning enhancements (R1-2205406; contact: CATT) |
RAN1 |
R2-2206810 |
Reply LS on expected AoA and AoD parameters (R1-2205619; contact: Nokia) |
RAN1 |
R2-2206814 |
Correction based upon Positioning RILs |
Ericsson, MediaTek, Intel, Huawei, Samsung, ZTE, Lenovo, vivo |
6.11.2.1 |
Latency enhancements |
|
R2-2204699 |
Discussion on the positioning MG activation deactivation MAC CE |
CATT |
R2-2204700 |
Correction on the positioning MG activation deactivation MAC CE |
CATT |
R2-2204701 |
Discussion on the cancel conditions of the triggered UL positioning MG activation/deactivation MAC CE |
CATT |
R2-2204702 |
Correction on the cancel conditions of the triggered UL positioning MG activation/deactivation MAC CE |
CATT |
R2-2204703 |
Correction on the cancel conditions of the triggered UL positioning MG activation/deactivation MAC CE |
CATT |
R2-2204704 |
Corrections on the TS38.305 |
CATT |
R2-2204742 |
Corrections on the TS38.321 |
CATT |
R2-2204996 |
Corrections on MAC CE for Positioning Measurement Gap |
Huawei, HiSilicon |
R2-2205309 |
Correction on pre-configured MG procedure in 38.321 |
ZTE, Sanechips |
R2-2205311 |
Discussion on the pre-configured MG signaling |
ZTE, Sanechips |
R2-2205579 |
Discussion on the handling of pre-MG for positioning |
vivo |
R2-2205656 |
Definition of positioning measurement gap activation/deactivation MAC CE |
Apple |
R2-2205764 |
Issues with PRS Processing Window Procedures |
Qualcomm Incorporated |
R2-2205766 |
Assistance Data Request for Multiple Area IDs |
Qualcomm Incorporated |
R2-2205804 |
Text Proposal to address UE request of Area Info and Broadcast of Area |
Ericsson, Fraunhofer IIS, Fraunhofer HHI, Lenovo, Motorola Mobility |
R2-2205808 |
Correction to activate pre-configured PPW Signaling |
Ericsson |
R2-2205809 |
Correction of PPW Activation/Deactivation Command MAC CE size description |
Ericsson |
R2-2205810 |
Clarification on PPW and MG configuration to the same UE and miscellaneous corrections |
Ericsson |
R2-2205812 |
UL MAC CE for preconfigured MG |
Ericsson |
R2-2205814 |
On PPW Configuration Release assistance info |
Ericsson |
R2-2206147 |
Summary of AI 6.11.2.1 on latency |
ZTE Corporation |
R2-2206255 |
Email discussion for Positioning Measurement Gap |
Huawei, HiSilicon |
R2-2206256 |
[AT118-e][635][POS] Cross-group alignment for PPW (Qualcomm) |
Qualcomm Incorporated |
R2-2206331 |
Text Proposal to address UE request of Area Info and Broadcast of Area |
Ericsson, Fraunhofer IIS, Fraunhofer HHI, Lenovo, Motorola Mobility |
R2-2206340 |
Summary of AI 6.11.2.1 on latency |
ZTE, Sanechips |
R2-2206388 |
LS on LocationMeasurementIndication contents and measurement gap parameters |
RAN2 |
6.11.2.2 |
RRC_INACTIVE |
|
R2-2204691 |
Further consideration on Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state |
CATT |
R2-2204692 |
[Draft] Rely LS on Positioning in RRC_INACTIVE |
CATT |
R2-2204693 |
Consideration on positioning SRS configuration for RRC_INACTIVE |
CATT |
R2-2205012 |
Correction to beam consolidation for posSRS in RRC_INACTIVE |
Huawei, HiSilicon |
R2-2205013 |
[H572] Correction for beam consolidation for TA validation in RRC_INACTIVE |
Huawei, HiSilicon |
R2-2205368 |
Corrections on Maintenance of Uplink Time Alignment |
Xiaomi |
R2-2205580 |
Discussion on the remaining issue about positioning in RRC_INACTIVE |
vivo |
R2-2206052 |
Summary of AI 6.11.2.2 on RRC_INACTIVE |
vivo |
R2-2206257 |
Report of [AT118-e][636][POS] Proposals for discussion from RRC_INACTIVE summary |
vivo |
R2-2206384 |
[I512] [I010] SRS Positioning configuration provided for SDT |
Intel Corporation, Ericsson |
R2-2206387 |
Draft LS to RAN3 on container for SRS configuration for positioning |
Intel |
R2-2206678 |
LS to RAN3 on container for SRS configuration for positioning |
RAN2 |
R2-2206774 |
LS to RAN3 on container for SRS configuration for positioning |
RAN2 |
6.11.2.3 |
On-demand PRS |
|
R2-2205007 |
[H011] TRP config for on-demand PRS |
Huawei, HiSilicon |
R2-2205011 |
[H057] Discussion on UE-initiated on-demand PRS |
Huawei, HiSilicon |
R2-2205581 |
Discussion on the mismatch between the on-demand PRS procedure of RAN2 and RAN3 |
vivo |
R2-2205805 |
On UE measurements to allow On-Demand PRS |
Ericsson, Nokia, Fraunhofer IIS, Fraunhofer HHI, Lenovo, Motorola Mobility |
R2-2206058 |
[Pre118-e][605][POS] Summary of AI 6.11.2.3 on on-demand PRS (Huawei) |
Huawei, HiSilicon |
R2-2206258 |
Email discussion for on-demand PRS |
Huawei, HiSilicon |
6.11.2.4 |
GNSS positioning integrity |
|
R2-2204997 |
Draft LS to SA1/SA2 on GNSS integrity |
Huawei, HiSilicon |
R2-2205017 |
Correction to stage2 on service level support for GNSS integrity |
Huawei, HiSilicon |
R2-2205488 |
Corrections on Positioning Integrity parameter table |
Samsung R&D Institute UK |
R2-2205815 |
Remaining issues for integrity |
Ericsson |
R2-2206037 |
[C002] Correction on the Note of the Protection Level (PL) |
CATT |
R2-2206067 |
[C002] Correction on the Note of the Protection Level (PL) |
CATT |
R2-2206092 |
Summary of GNSS Positioning Integrity AI 6.11.2.4 |
Ericsson |
R2-2206260 |
[AT118-e][639][POS] Collection of views on integrity proposals (Ericsson) |
Ericsson |
R2-2206389 |
LS on GNSS integrity |
RAN2 |
R2-2206681 |
[AT118-e][639][POS] Collection of views on integrity proposals (Ericsson) |
Ericsson |
6.11.2.5 |
A-GNSS enhancements |
|
R2-2204689 |
Correction on the reference file of BDS Signal B3I |
CATT, CAICT |
R2-2204690 |
Correction on the reference file of BDS Signal B3I |
CATT, CAICT |
6.11.2.6 |
Accuracy enhancements |
|
R2-2204696 |
Discussion on R17 positioning enhancement impacts on stage-2 specification |
CATT |
R2-2204697 |
Introduction of R17 NRPPa related positioning enhancement to TS38.305 |
CATT |
R2-2204698 |
[Draft] LS to RAN3 on introduction of R17 NRPPa related positioning enhancement to TS38.305 |
CATT |
R2-2204705 |
Discussion on the LS on the framework of UE/TRP Rx TEG |
CATT |
R2-2204706 |
Discussion on the left issues on UE TxTEG report in RRC and LPP protocols |
CATT |
R2-2204707 |
[C243] Correction on the UE TxTEG report in TS 38.331 |
CATT |
R2-2204708 |
[C013][C014][C015][C016][C017]Corrections on the UE TxTEG report in TS 37.355 |
CATT |
R2-2204987 |
[C011] Correction on the beam antenna information for DL-AoD |
CATT |
R2-2204988 |
[C012] Correction on the selected on-demand PRS configuration for hybrid positioning |
CATT |
R2-2205003 |
[H028] Correction to measurement with multiple TEGs |
Huawei, HiSilicon |
R2-2205004 |
[H026][H027][H029][H030] Correction to LOS-NLOS indication |
Huawei, HiSilicon |
R2-2205005 |
[H006][H040] Correction to adjacent beam assistance data |
Huawei, HiSilicon |
R2-2205008 |
[H013] Correction to TRP beam antenna info |
Huawei, HiSilicon |
R2-2205016 |
[H060] Correction on DL-AoD additional measurement |
Huawei, HiSilicon |
R2-2205307 |
[H026][H029][Z004]Discussion on LOS NLOS indicator in LPP spec |
ZTE, Sanechips |
R2-2205308 |
[Z003][H025]Signaling of measurement instances |
ZTE, Sanechips |
R2-2205369 |
Discussion on the Periodic Tx TEG reporting and preconfigured MG |
Xiaomi |
R2-2205370 |
Remaining issues on positioning reference unit |
Xiaomi |
R2-2205582 |
Discussion on remaining issue about accuracy enhancements |
vivo |
R2-2205654 |
On periodic UE Tx TEG reporting |
Apple |
R2-2205730 |
Discussion on UE TX TEG association reporting |
InterDigital, Inc. |
R2-2205806 |
Remaining Issues on TEG reporting; failure Handling |
Ericsson |
R2-2205807 |
Update of signalling in stage 2 to align with NRPPa |
Ericsson |
R2-2206051 |
[H026][H029][Z004]Discussion on LOS NLOS indicator in LPP spec |
ZTE, Sanechips |
R2-2206083 |
[Pre118-e][607][POS] Summary of AI 6.11.2.6 on accuracy (CATT) |
CATT |
R2-2206259 |
[AT118-e][638][POS] Tx TEG and LOS/NLOS aspects (CATT) |
CATT |
R2-2206333 |
[Pre118-e][607][POS] Summary of AI 6.11.2.6 on accuracy (CATT) |
CATT |
6.11.2.7 |
UE capabilities |
|
R2-2204933 |
Positioning UE capabilities |
Intel Corporation |
R2-2205009 |
[H022] Summary of R2-agreed capabilities for R17 POSenh |
Huawei, HiSilicon |
R2-2206330 |
On Resolving PPW Capability discrepancy |
Ericsson |
R2-2206393 |
Report of [AT118-e][627][POS] Positioning UE capabilities (Intel) |
Intel Corporation |
R2-2206396 |
37.355 CR for the positioning capablities |
Intel Corporation |
R2-2206397 |
38.331 CR for the positioning capablities |
Intel Corporation |
R2-2206398 |
38.306 CR for the positioning capablities |
Intel Corporation |
6.11.2.8 |
LPP ASN.1 issues |
|
R2-2204932 |
I004 Validity area for preconfigured AD |
Intel Corporation |
R2-2205010 |
[H042][H004][H012][H025] Draft LS to R1 for remaining issues |
Huawei, HiSilicon |
R2-2205430 |
Discussion of the need of the area ID for the pre-configured assistance data |
OPPO |
R2-2205583 |
[V003] Discussion on the format of pre-configuration |
vivo |
R2-2205584 |
[V004][V006]Discussion on LPP ASN.1 issues |
vivo |
R2-2205813 |
LPP RIL E603 and 604 on associated TRP |
Ericsson |
R2-2205843 |
Rel-17 LPP RIL |
Qualcomm Incorporated |
R2-2205844 |
Rel-17 LPP ASN1 Review File |
Qualcomm Incorporated |
R2-2205846 |
Editorial Corrections |
Qualcomm Incorporated |
R2-2205847 |
LPP Updates and ASN.1 Corrections |
Qualcomm Incorporated (Rapporteur) |
R2-2206252 |
[AT118-e][631][POS] Remaining PropDisc LPP RIL items (Qualcomm) |
Qualcomm Incorporated |
R2-2206326 |
Rel-17 LPP RIL |
Qualcomm Incorporated |
R2-2206327 |
Rel-17 LPP ASN1 Review File |
Qualcomm Incorporated |
R2-2206328 |
LPP Updates and ASN.1 Review |
Qualcomm Incorporated |
R2-2206390 |
LS on expected AoA and AoD parameters |
RAN2 |
6.11.2.9 |
Positioning RRC ASN.1 issues |
|
R2-2204998 |
[H568] Correction for periodic TEG reporting |
Huawei, HiSilicon |
R2-2204999 |
[H570] Correction for cell reselection for SRS in RRC_INACTIVE |
Huawei, HiSilicon |
R2-2205000 |
[H566][H567] Correction for Location Measurement Indication |
Huawei, HiSilicon |
R2-2205001 |
[H563]Correction for reception of RRCRelease by the UE |
Huawei, HiSilicon |
R2-2205048 |
[S854][S855][S856] Handling preconfigured gaps for POS upon a handover |
Samsung |
R2-2205049 |
[S851][S852][S853] Type and priority configuration of PPW |
Samsung |
R2-2205310 |
Correction on pre-configured MG procedure in 38.331 |
ZTE, Sanechips |
R2-2205498 |
[E066] Correction on structure of UEPositioningAssistInfo message contents for reducing unnecessary data transmission |
Samsung R&D Institute UK |
R2-2205585 |
Discussion on positioning RRC ASN.1 issues |
vivo |
R2-2205811 |
[RILE064] Moving TEG Reporting Configuration from SRS-Config to RRCReconfig |
Ericsson |
R2-2205816 |
[RIL E060] On removal of Editors' Note for SRS Inactive mode procedure during RRC Resume |
Ericsson |
R2-2205817 |
[RIL E060] Editors Note Discussion on RRC Procedure Structure on section |
Ericsson |
R2-2205857 |
RRC Positioning RIL Summary |
Ericsson |
R2-2206400 |
RRC Positioning RIL Summary |
Ericsson |
6.11.3 |
Other |
|
R2-2205006 |
[H056] Correction to need code in posSIB_R17 |
Huawei, HiSilicon |
R2-2205655 |
Stage-2 positioning corrections |
Apple |
6.12.1.1 |
LS in |
|
R2-2204410 |
LS reply on the coordination between gNBs supporting RedCap UEs (R3-221396; contact: Ericsson) |
RAN3 |
R2-2204422 |
LS on operation with and without SSB for RedCap UE (R1-2202886; contact: Ericsson) |
RAN1 |
R2-2204475 |
LS on configuring margin for 1 Rx RedCap UEs (R4-2206951; contact: Ericsson) |
RAN4 |
R2-2204476 |
Reply LS on UE capabilities for RedCap from RRM perspective (R4-2206977; contact: Ericsson) |
RAN4 |
R2-2204486 |
LS on NCD-SSB issues for RedCap UE (R4-2207104; contact: Ericsson) |
RAN4 |
R2-2204487 |
LS on RRM relaxation for Redcap (R4-2207109; contact: vivo) |
RAN4 |
R2-2204502 |
LS on FR2 RedCap UE (R4-2206545; contact: Ericsson) |
RAN4 |
R2-2204619 |
Discussion on RAN4 LS on FR2 RedCap UE |
Futurewei Technologies |
R2-2204620 |
Discussion on RAN4 LS on RRM Relaxation for RedCap |
Futurewei Technologies, Xiaomi Communications, OPPO, Vivo, Ericsson, Qualcomm |
R2-2204810 |
[Draft] Reply LS to RAN4 on RRM relaxation |
vivo |
R2-2206018 |
[DRAFT] Reply LS on configuring margin for 1 Rx RedCap UEs |
Ericsson |
R2-2206019 |
[DRAFT] Reply LS on NCD-SSB issues for RedCap UE |
Ericsson |
R2-2206020 |
[DRAFT] Reply LS on FR2 RedCap UE |
Ericsson |
R2-2206417 |
Reply LS on NCD-SSB issues for RedCap UE |
Ericsson |
R2-2206418 |
Reply LS to RAN4 on RRM relaxation |
RAN2 |
R2-2206419 |
Draft Reply LS on operation with and without SSB for RedCap UE |
ZTE |
R2-2206504 |
Reply LS on configuring margin for 1 Rx RedCap Ues |
RAN2 |
R2-2206611 |
Reply LS on operation with and without SSB for RedCap UE |
RAN2 |
R2-2206662 |
Reply LS on NCD-SSB issues for RedCap UE |
RAN2 |
R2-2206705 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times (R1-2205535; contact: Ericsson) |
RAN1 |
R2-2206748 |
LS on CGI reading with autonomous gaps for RedCap (R4-2210593; contact: Ericsson) |
RAN4 |
R2-2206749 |
LS on measurement capability for RedCap (R4-2210594; contact: CMCC) |
RAN4 |
R2-2206750 |
Reply LS on RRM relaxation for Redcap (R4-2210598; contact: vivo) |
RAN4 |
R2-2206751 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times (R4-2210599; contact: Ericsson) |
RAN4 |
6.12.1.2 |
Rapporteur CRs |
|
R2-2204811 |
Miscellaneous CR on TS 38.321 for RedCap |
vivo |
R2-2204926 |
Draft 38.306 CR for the RedCap capablities |
Intel Corporation |
R2-2204927 |
Draft 38.331 CR for the RedCap capablities |
Intel Corporation |
R2-2205784 |
Corrections on RedCap in TS 38.300 |
Nokia, Nokia Shanghai Bell, Huawei |
R2-2206021 |
Miscellaneous corrections for RedCap WI |
Ericsson |
R2-2206022 |
RedCap WI ASN1 RIL list |
Ericsson |
R2-2206023 |
Miscellaneous corrections for RedCap WI |
Ericsson |
R2-2206203 |
Corrections on RedCap in TS 38.300 |
Nokia, Nokia Shanghai Bell, Huawei |
R2-2206215 |
Miscellaneous corrections for RedCap WI |
Ericsson |
R2-2206216 |
Miscellaneous corrections for RedCap WI |
Ericsson |
R2-2206217 |
Miscellaneous CR on TS 38.321 for RedCap |
vivo |
R2-2206267 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times |
RAN2 |
R2-2206615 |
Draft 38.306 CR for the RedCap capablities |
Intel Corporation |
R2-2206616 |
Draft 38.331 CR for the RedCap capablities |
Intel Corporation |
R2-2206706 |
Miscellaneous corrections for RedCap WI |
Ericsson, Samsung |
6.12.2.1 |
NCD-SSB aspects |
|
R2-2204544 |
Handover to BWP without CD-SSB |
ZTE Corporation, Sanechips |
R2-2204547 |
Discussion on serving cell measurements on NCD-SSB |
ZTE Corporation, Sanechips |
R2-2204812 |
Discussion on NCD-SSB for RedCap UEs |
vivo, Guangdong Genius |
R2-2205038 |
Discussion on NCD-SSB aspects for RedCap UE |
Huawei, HiSilicon |
R2-2205285 |
[J002] Clarification on reference value in connected RRM relaxation critrion |
Sharp |
R2-2205512 |
Discussion on BWP operation without bandwidth restriction and NCD SSB |
Vodafone GmbH, Deutsche Telekom, Qualcomm |
R2-2205522 |
Aspects related to the use of NCD-SSB |
MediaTek Inc. |
R2-2205636 |
Discussion on NCD-SSB handling at handover |
Apple |
R2-2205771 |
About paging monitoring in BWP#0 without CD-SSB |
ZTE Corporation, Sanechips |
R2-2206032 |
Further discussion on SI acquisition in RedCap-specific BWP |
Qualcomm Incorporated |
R2-2206033 |
Measurement object configuration with NCD-SSB |
Qualcomm Incorporated |
R2-2206143 |
[Pre118-e][105][RedCap] Summary of AI 6.12.2.1 on NCD-SSB aspects |
ZTE Corporation |
R2-2206195 |
[AT118-e][105][RedCap] NCD-SSB aspects |
ZTE Corporation |
R2-2206204 |
[AT118-e][105][RedCap] NCD-SSB aspects—Phase 2 |
ZTE Corporation |
R2-2206414 |
[AT118-e][105][RedCap] NCD-SSB aspects—Phase 3 |
ZTE Corporation |
6.12.2.2.1 |
Known Corrections |
|
R2-2204723 |
Discussion on inter-RAT mobility from LTE to NR |
OPPO |
R2-2204724 |
Discussion on including RedCap UE’s capability in the UERadioPagingInformation inter-node message |
OPPO |
R2-2204725 |
[O374] correction on RedCap UE’s cell barring |
OPPO |
R2-2204736 |
[O372] Discussion on prohibit timer for UAI for RRM relaxation fulfilment indication |
OPPO |
R2-2204737 |
[O377] Correction to 38.331 on UAI for RRM relaxation fulfilment indication |
OPPO |
R2-2204813 |
[V166] Including RedCap Capability in the UERadioPagingInformation Inter-Node Message |
vivo, Guangdong Genius |
R2-2204814 |
[V170] Discussion on Inter-RAT Mobility from LTE to NR for RedCap |
vivo, Guangdong Genius |
R2-2204815 |
Coexistence of Rel-16 and Rel-17 RRM relaxation criteria |
vivo, Guangdong Genius |
R2-2204929 |
RRC open issues on Rel17 RedCap WI |
Intel Corporation |
R2-2205036 |
Inter-RAT mobility from LTE to NR |
Huawei, HiSilicon |
R2-2205037 |
Paging capability and cell selection related to R4 LS |
Huawei, HiSilicon |
R2-2205047 |
Correction on the DRX cycle of the UE for eDRX |
NEC |
R2-2205089 |
Co-existence of Rel-16 and Rel-17 RRM relaxation |
Samsung |
R2-2205091 |
Correction on RRM relaxation in RRC_CONNECTED (RIL#:951) |
Samsung |
R2-2205284 |
[J001] Correction on Srxlev in connected RRM relaxation critrion |
Sharp, Huawei, HiSilicon |
R2-2205770 |
Consideration on RedCap access indication |
ZTE Corporation, Sanechips |
R2-2205904 |
Handover from E-UTRA from legacy eNB to legacy gNB |
Ericsson |
R2-2206059 |
[X115]38.331 Corrections on UE's behaviour of getting SIB1 for Redcap |
Xiaomi Communications |
R2-2206060 |
[X119][X114]Discussion on PDCCH-ConfigCommon for Redcap |
Xiaomi Communications |
R2-2206061 |
[X119][X114]38.331 Corrections on PDCCH-ConfigCommon for Redcap |
Xiaomi Communications |
R2-2206062 |
[X120]38.331 Corrections on Need code of RedCap-specific initial DL BWP for handover |
Xiaomi Communications |
R2-2206192 |
Report from [AT118-e][102][RedCap] RRC CR (Ericsson) |
Ericsson (Rapporteur) |
R2-2206199 |
Report of [AT117-e][113][RedCap] RRM relaxation (vivo) |
vivo |
R2-2206205 |
Report of [AT118-e][109][RedCap] RRM relaxation (vivo) – second round |
vivo |
R2-2206218 |
Report from [AT118-e][102][RedCap] RRC CR (Ericsson) – PH2 |
Ericsson (Rapporteur) |
R2-2206415 |
Report of [AT118-e][109][RedCap] RRM relaxation (vivo) – final round |
vivo |
6.12.2.2.2 |
Other |
|
R2-2204541 |
[S953] SI Request for RedCap UEs |
Samsung Electronics Co., Ltd |
R2-2204816 |
Correction on RLM for RedCap |
vivo, Guangdong Genius |
R2-2204819 |
UE Capability and System Information for eDRX |
vivo, Guangdong Genius |
R2-2204928 |
Draft 38.304 CR for the eDRX handling |
Intel Corporation |
R2-2204936 |
I051 support of RedCap based on intraFreqReselectionRedCap |
Intel Corporation |
R2-2204979 |
Cell reselection priority for RedCap (RIL#: S952) |
Samsung |
R2-2205039 |
[Draft] LS on the maximum PTW length of IDLE eDRX |
Huawei, HiSilicon |
R2-2205090 |
Corrections on eDRX |
Samsung |
R2-2205150 |
Correction on DRX cycle of the UE for eDRX |
NEC |
R2-2205337 |
Other CP aspects for DRX cycle |
LG Electronics Finland |
R2-2205523 |
SIB validity with eDRX |
MediaTek Inc. |
R2-2205613 |
38.304 Corrections on Redcap UE's behavior on cellbar |
Xiaomi Communications,Huawei, HiSilicon |
R2-2205769 |
Corrections on eDRX |
ZTE Corporation, Sanechips |
R2-2205783 |
Miscellaneous RedCap corrections |
Nokia, Nokia Shanghai Bell |
R2-2205785 |
HD-FDD RedCap support in system information |
Nokia, Nokia Shanghai Bell |
R2-2205786 |
RSRP thresholds for 1 Rx RedCap Ues |
Nokia, Nokia Shanghai Bell |
R2-2206024 |
Configuring margin for 1 Rx RedCap UEs |
Ericsson |
R2-2206080 |
[H507] Corrections on cell re-selection measurements during RRC setup/resume |
Huawei, HiSilicon |
R2-2206081 |
[H511] Corrections on redcapAccessRejected |
Huawei, HiSilicon |
R2-2206082 |
[H513 H516 H520 H524 H525 H526 H527] Corrections on RedCap initial BWP |
Huawei, HiSilicon |
R2-2206213 |
Report of [AT118-e][115][RedCap] 38.304 CR (Samsung) |
Samsung |
R2-2206620 |
LS on the maximum PTW length of IDLE eDRX |
RAN2 |
R2-2206688 |
Report of [AT118-e][115][RedCap] 38.304 CR (Samsung) (Phase 2) |
Samsung |
6.12.3.1 |
MAC aspects |
|
R2-2204817 |
Discussion on MAC aspects for RedCap |
vivo, Guangdong Genius |
R2-2205040 |
Discussion on MAC RACH related issues for RedCap UE |
Huawei, HiSilicon |
R2-2205487 |
Corrections on BWP operation for RedCap UE |
LG Electronics Inc. |
R2-2206214 |
[AT118-e][116][RedCap] MAC aspects (vivo) |
vivo |
R2-2206618 |
TP for SI request |
Samsung |
6.12.4.1 |
Known remaining issues |
|
R2-2204738 |
Clarification on HD-FDD support for RedCap |
OPPO |
R2-2204818 |
Discussion on capability for RedCap |
vivo, Guangdong Genius |
R2-2204925 |
Open issues on RedCap capabilities |
Intel Corporation |
R2-2205637 |
RedCap UE power class 7 signaling |
Apple |
R2-2205638 |
RedCap UE power class 7 signaling |
Apple |
R2-2205787 |
On RedCap UE capabilities |
Nokia, Nokia Shanghai Bell |
R2-2206025 |
Introduction of FR2 RedCap UE |
Ericsson |
R2-2206026 |
Introduction of FR2 RedCap UE |
Ericsson |
R2-2206027 |
Introduction of FR2 RedCap UE |
Ericsson |
R2-2206200 |
Report of [AT118-e][110][RedCap] UE capabilities (Intel) |
Intel Corporation |
R2-2206219 |
Report of [AT118-e][110][RedCap] UE capabilities (Intel) |
Intel Corporation |
6.13.1 |
Organizational |
|
R2-2204405 |
Reply LS on UE context keeping in the source cell (R3-212944; contact: Ericsson) |
RAN3 |
R2-2204406 |
LS Reply on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (R3-214429; contact: Ericsson) |
RAN3 |
R2-2204407 |
Reply LS on scenarios need to be supported for MRO in SCG Failure Report (R3-216159; contact: Samsung) |
RAN3 |
R2-2204408 |
Reply LS on Area scope configuration and Frequency band info in MDT configuration (R3-221178; contact: Huawei) |
RAN3 |
R2-2204409 |
Reply LS to SA5 on beam measurement reports (R3-221383; contact Ericsson) |
RAN3 |
R2-2204412 |
Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-213499; contact: Ericsson) |
SA5 |
R2-2204413 |
Reply LS on Report Amount for M4, M5, M6, M7 measurements (S5-214523; contact: Nokia) |
SA5 |
R2-2204414 |
Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-215493; contact: Ericsson) |
SA5 |
R2-2204415 |
Reply LS on the Beam measurement reports for the MDT measurements (S5-216628; contact: Ericsson) |
SA5 |
R2-2204448 |
LS on UP measurements for Successful Handover Report (R3-212935; contact: Ericsson) |
RAN3 |
R2-2204498 |
Reply LS on MDT M6 calculation for split bearers in MR-DC (R3-222868; contact: Ericsson) |
RAN3 |
R2-2206744 |
LS on M6 Delay Threshold (R3-224079; contact: CATT) |
RAN3 |
6.13.2 |
CRs and Rapporteur Resolutions |
|
R2-2205903 |
Miscellaneous rapporteur corrections for SON-MDT |
Ericsson |
R2-2206344 |
Summary of [Pre118-e][801][SON/MDT] 38.331 CR and rapporteur resolutions (Ericsson) |
Ericsson |
R2-2206345 |
Miscellaneous rapporteur corrections for SON-MDT |
Ericsson |
R2-2206863 |
Miscellaneous rapporteur corrections for SON-MDT |
Ericsson |
6.13.3 |
SON Corrections |
|
R2-2204876 |
[N030] Correction to conditions determining successful handover report |
Nokia, Nokia Shanghai Bell |
R2-2204877 |
[N028] Correction to SuccessHO-Config |
Nokia, Nokia Shanghai Bell |
R2-2204878 |
Correction to Mobility History Information setting [N094][N095][E122][H072] |
Nokia, Nokia Shanghai Bell |
R2-2204879 |
Corrections on Rel-17 RLFreport |
Nokia, Nokia Shanghai Bell |
R2-2204880 |
Clarification on SHR for DAPS HO |
Nokia, Nokia Shanghai Bell |
R2-2204883 |
RIL: [S702] [S703] [S704] [S705] [S706] [S707] [S708] |
Samsung |
R2-2204884 |
RIL: [S709][S710][S711][S712] |
Samsung |
R2-2204885 |
RIL: [S713][S714][S715]Using ENUMERATED {true} instead of BOOLEAN |
Samsung |
R2-2204938 |
[C320] Add SgNB RA Report related Information |
CATT |
R2-2204939 |
Addition of SON Features Enhancement in Stage 2 |
CATT |
R2-2204940 |
[C326] Clarification on CHO Candidate Cell List in SHR |
CATT |
R2-2204941 |
[C327] Correction on CHO Information Logging for Mobility from NR Failure |
CATT |
R2-2204942 |
[C328] Clarification on CHO Information Logging in Neighbour Cell Measurement in RLF Report |
CATT |
R2-2204966 |
[B180] TP for reporting CHO execution condition in RLF report |
Lenovo |
R2-2204967 |
[B181] TP for reporting time information for SCG failure |
Lenovo |
R2-2205046 |
[W006] Correction on the generation and discarding of SHR |
NEC |
R2-2205072 |
Discussion on SON with DAPS [S704] |
Huawei, HiSilicon |
R2-2205074 |
Introduction of SHR in TS 38.300 |
Huawei, HiSilicon |
R2-2205075 |
Corrections on TS 37.320 for SON and MDT |
Huawei, HiSilicon |
R2-2205361 |
[Z401][Z413] Consideration on multiple CEF report |
ZTE Corporation, Sanechips |
R2-2205362 |
[Z421] Consideration on RA report |
ZTE Corporation, Sanechips |
R2-2205363 |
[Z408] Consideration on RLF-report for CHO-DAPS |
ZTE Corporation, Sanechips |
R2-2205364 |
Draft CR to 38331 on RLF-report |
ZTE Corporation, Sanechips |
R2-2205704 |
HO related SON corrections |
Qualcomm Incorporated |
R2-2205892 |
Corrections to 2-step RA Report [E076][E078] |
Ericsson |
R2-2205893 |
Corrections to Mobility History Information [E120][E121][E122] |
Ericsson |
R2-2205894 |
Corrections to mobility history information reporting [E120, E121, E122] |
Ericsson |
R2-2205901 |
Including source-related RA-Information in SHR [E079] |
Ericsson |
R2-2206098 |
[H070, H095, H105, H106, H107, H108] SON with CHO |
Huawei, HiSilicon |
R2-2206099 |
[H069] TAC for RLF report |
Huawei, HiSilicon |
R2-2206100 |
[H074] UP interruption time |
Huawei, HiSilicon |
R2-2206101 |
[H096] SN RACH reporting issue |
Huawei, HiSilicon |
R2-2206102 |
[H099, H100] 2-step RA related issues |
Huawei, HiSilicon |
R2-2206103 |
[H097] msgA-PUSCH-PayloadSize indication |
Huawei, HiSilicon |
R2-2206104 |
[H076] triggeredEvent related issues |
Huawei, HiSilicon |
R2-2206132 |
Issues with nested MHI [H098][N094][N095][E121][H071][E122] |
Nokia, Nokia Shanghai Bell |
R2-2206464 |
Summary of RILs discussion |
Ericsson, Huawei |
R2-2206569 |
Summary of RILs discussion – Phase 3 |
Ericsson, Huawei |
6.13.4 |
MDT Corrections |
|
R2-2204672 |
[O700][O701] RRC corrections for MDT |
OPPO |
R2-2204943 |
The Correction on TS37.320 |
CATT |
R2-2205076 |
Corrections on TS.38.314 for the delay measurement for split bearer |
Huawei, HiSilicon |
R2-2205686 |
TP on signalling based logged MDT override protection in inter-PLMN scenarios [RIL number E069] |
Ericsson |
R2-2205687 |
TP on IDC issues in logged MDT [RIL number E074] |
Ericsson |
R2-2205688 |
TP on multiple CEF reports [RIL number E075 and E123] |
Ericsson |
R2-2205689 |
TP on L2 measurements for total RAN delay calculation |
Ericsson |
R2-2205736 |
[S716] Remaining issues on multiple CEF reports |
Samsung Electronics Co., Ltd |
R2-2205738 |
[S701] Remaining issues on signalling based MDT protection |
Samsung Electronics Co., Ltd |
R2-2206667 |
Corrections on TS 38.314 |
Huawei, HiSilicon |
R2-2206668 |
Corrections on TS37.320 |
CATT |
R2-2206676 |
Report of [AT118-e][805][SON/MDT] Corrections on TS.38.314 (Huawei) |
Huawei |
6.13.5 |
UE Capabilities |
|
R2-2204944 |
[C329] Add MDT related UE Capabilities of EMR |
CATT |
R2-2204945 |
Add MDT related UE Capabilities of EMR |
CATT |
R2-2205073 |
Corrections on TS 38.306 for UE capabilities for SON and MDT |
Huawei, HiSilicon |
R2-2205705 |
SON MDT UE Capabilities |
Qualcomm Incorporated |
R2-2206445 |
Report of [AT118e][802][SONMDT] UE capabilities related to SONMDT (CATT) |
CATT |
R2-2206450 |
Add Early Measurement related MDT UE Capability and Corrections in TS38.306 |
CATT |
R2-2206451 |
Add Early Measurement related MDT UE Capability and Corrections in TS38.306 |
CATT |
6.13.6 |
Other |
|
R2-2204664 |
CR to 38314 on RA preamble measurement |
ZTE Corporation, Sanechips, CMCC |
R2-2205222 |
Discussion on PSCell MHI recording for RRC inactive state |
Sharp |
R2-2205567 |
Addition of Last Serving Beam in RLF Report |
Nokia, Nokia Shanghai Bell |
6.14.1.1 |
Organizational |
|
R2-2204449 |
LS on the specification of AT commands for NR QoE (C1-222058; contact: Ericsson) |
CT1 |
R2-2204500 |
LS on RAN3 agreements for NR QoE (R3-222890; contact: China Unicom) |
RAN3 |
R2-2204528 |
Reply LS on UE capabilities for NR QoE (S4-220534; contact: Ericsson) |
SA4 |
R2-2206797 |
Reply LS on UE capabilities for NR QoE (C1-224008; contact: Apple) |
CT1 |
R2-2206799 |
Reply LS on NR QoE (C1-224182; contact: Huawei) |
CT1 |
6.14.1.2 |
CR Rapporteur Resolutions |
|
R2-2205439 |
Correction CR for QoE measurements |
Ericsson |
R2-2206119 |
RIL List v207 for QoE |
L.M. Ericsson Limited |
R2-2206604 |
Summary of [AT118-e][078][QoE] RRC (Ericsson) for 6.14 |
Ericsson |
R2-2206703 |
LS on questions on RAN visible QoE |
RAN2 |
R2-2206832 |
Correction CR for QoE measurements |
Ericsson |
R2-2206833 |
LS on questions on RAN visible QoE |
RAN2 |
R2-2206846 |
Correction CR for QoE Measurement Collection in NR |
Ericsson |
6.14.3 |
Corrections |
|
R2-2204591 |
38.300 CR Correction for Introduction of QoE measurements in NR |
China Unicom, Huawei, HiSilicon, Ericsson, Apple |
R2-2204847 |
Corrections to stage 2 NR QoE description |
Lenovo |
R2-2204848 |
Discussion on NR QoE issues |
Lenovo |
R2-2204874 |
[N024] Correction to storage of application layer measurements during Pause |
Nokia, Nokia Shanghai Bell |
R2-2204875 |
[N023] Correction to paused application layer measurements reporting |
Nokia, Nokia Shanghai Bell |
R2-2205085 |
Correction on UE configuration for QoE (RIL#: S751) |
Samsung |
R2-2205086 |
Class 0 corrections on QoE configuration and report |
Samsung |
R2-2205087 |
Further corrections on QoE configuration |
Samsung |
R2-2205088 |
Further corrections on QoE report |
Samsung |
R2-2205283 |
Discussion on session stop during QoE reporting suspend |
Qualcomm Incorporated |
R2-2205334 |
Clarification on session stop during QoE reporting suspend |
Qualcomm Incorporated |
R2-2205440 |
Discussion on naming of QoE measurements |
Ericsson |
R2-2205441 |
Discussion on RIL issue E138 related to handover |
Ericsson |
R2-2205442 |
Discussion on RIL issues H088 and H089 related to RAN visible QoE |
Ericsson |
R2-2205443 |
Discussion on RIL issues H054 and H094 |
Ericsson |
R2-2205649 |
Area scope and mobility management |
Apple |
R2-2205943 |
Corrections to TS 38.300 for NR QoE |
Huawei, HiSilicon |
R2-2206128 |
Discussion on applicationLayerSessionStatus (RIL: H056) |
Huawei, HiSilicon |
R2-2206129 |
Clarifications for buffer level reporting (RIL: H088) |
Huawei, HiSilicon |
R2-2206130 |
Corrections for RAN visible QoE (RIL: H089, H090, H909) |
Huawei, HiSilicon |
R2-2206546 |
Report of [AT118-e][079][QoE] 38300 |
China Unicom (Rapporteur) |
R2-2206547 |
38.300 CR Correction for Introduction of QoE measurements in NR |
China Unicom, Huawei, HiSilicon, Ericsson, Apple |
6.14.4 |
UE capabilities |
|
R2-2204849 |
Introduction of AS layer memory size for QoE paused measurement reports |
Lenovo |
R2-2205944 |
Correction on QoE capabilities dependencies |
Huawei, HiSilicon |
R2-2206536 |
Report for [AT118-e][080][QoE] UE capabilities (CMCC) |
CMCC |
R2-2206537 |
Minor Changes to NR QoE UE capabilities |
CMCC |
6.15.1 |
Organizational |
|
R2-2204525 |
Reply LS on Tx Profile (S2-2203595; contact: LGE) |
SA2 |
R2-2204644 |
Introduction of UE capability for Rel-17 sidelink |
OPPO |
R2-2205952 |
Miscellaneous Corrections to eSL |
InterDigital (Rapporteur) |
R2-2206133 |
Misc Class 0 corrections on TS 38.331 for SL enhancement |
Huawei, HiSilicon |
R2-2206134 |
Misc Class 1 Class 2 corrections on TS 38.331 for SL enhancement |
Huawei, HiSilicon |
R2-2206135 |
Summary of pre-discussion on RIL issues |
Huawei, HiSilicon |
R2-2206138 |
Rapporteur resolution for various RILs |
Huawei, HiSilicon |
R2-2206299 |
Reply LS to SA2 on Tx Profile |
RAN2 |
R2-2206300 |
Summary of [AT118-e][706][V2X/SL] RRC corrections (Huawei) |
Huawei, HiSilicon |
R2-2206301 |
Corrections for SL enhancements |
Huawei, HiSilicon |
R2-2206302 |
[AT118-e][707][V2X/SL] MAC corrections (LG) |
LG (Rapporteur) |
R2-2206303 |
Merged CRs on user plane aspects for SL DRX |
LG Electronics France |
R2-2206306 |
Misc corrections for SL enhancements |
Huawei, HiSilicon |
R2-2206307 |
Introduction of UE capability for Rel-17 sidelink |
OPPO |
R2-2206308 |
Summary of [AT118-e][711][V2X/SL] UE capability (OPPO) |
OPPO |
R2-2206310 |
Summary of 2nd round [AT118-e][706][V2X/SL] RRC corrections (Huawei) |
Huawei, HiSilicon |
R2-2206311 |
Corrections for SL enhancements |
Huawei, HiSilicon |
R2-2206312 |
LS on RRC parameters for IUC Scheme 1 and default CBR configuration |
RAN2 |
R2-2206315 |
Introduction of UE capability for Rel-17 sidelink |
OPPO |
R2-2206316 |
LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig |
RAN2 |
R2-2206317 |
Introduction of capability filter for Rel-17 sidelink |
OPPO |
R2-2206318 |
Corrections for SL enhancements |
Huawei, HiSilicon |
R2-2206319 |
Correction on user plane aspects for SL enhancement |
LG Electronics |
R2-2206320 |
Miscellaneous Corrections to eSL |
InterDigital |
R2-2206324 |
Miscellaneous Corrections to eSL |
InterDigital |
R2-2206378 |
Corrections for SL enhancements |
Huawei, HiSilicon |
R2-2206553 |
Reply LS on the inter-UE coordination mechanism (R1-2205400; contact: vivo) |
RAN1 |
R2-2206641 |
Introduction of capability filter for Rel-17 sidelink |
OPPO |
R2-2206865 |
Corrections for SL enhancements |
Huawei, HiSilicon |
6.15.2.1 |
Control plane procedure for UC DRX |
|
R2-2204578 |
Discussion on left issues on control plane procedure for UC DRX |
OPPO |
R2-2204643 |
Correction on [O099] |
OPPO |
R2-2204861 |
Discussion and TP for correction on RX UE reject behaviour |
Huawei, HiSilicon |
R2-2204862 |
Consideration on active time during uincast connection establishment |
Huawei, HiSilicon |
R2-2204954 |
Consideration for Control Plane Procedure for UC DRX |
CATT |
R2-2204955 |
Correction on the SL Active Time |
CATT |
R2-2204970 |
Remaining issues on SL DRX UC CP aspects for UC procedure |
Lenovo |
R2-2204971 |
Remaining issues for user plane of sidelink enhancement |
Lenovo |
R2-2205096 |
Discussion on the case that no SL DRX configuration is received from TX UE |
ZTE Corporation, Sanechips |
R2-2205097 |
Discussion on remaining issues for SL DRX rejection |
ZTE Corporation, Sanechips |
R2-2205106 |
[Z684]Correction on Destination ID list |
ZTE Corporation, Sanechips |
R2-2205116 |
remaining issues for control plane procedure for UC DRX |
LG Electronics France |
R2-2205148 |
Discussion on Rx UE’s rejection for SL DRX configuration |
NEC Corporation |
R2-2205178 |
Remaining control procedure of SL DRX |
Ericsson |
R2-2205263 |
Remaining issues on CP procedure for UC DRX |
vivo |
R2-2205264 |
Uu RRC impact by SL-DRX rejection from RX UE |
vivo |
R2-2205315 |
Discussion on UC sidelink DRX reject procedure |
Xiaomi |
R2-2205317 |
[X202][H663] Discussion on how RX UE to report accepted SL DRX and interested QoS |
Xiaomi |
R2-2205346 |
Correction on control plane |
ZTE Corporation, Sanechips |
R2-2205347 |
Correction on [Z677,Z680] |
ZTE Corporation, Sanechips |
R2-2205534 |
DRX configuration reject |
Samsung |
R2-2205605 |
Correction of SL DRX for SL discovery |
Samsung |
R2-2205606 |
Correction of SL DRX for L2 U2N Relay |
Samsung |
R2-2205706 |
Discussion on Procedure for UC SL DRX |
Qualcomm India Pvt Ltd |
R2-2205782 |
[E101] Correction on resource pool handling |
Ericsson |
R2-2205790 |
Open issues for SL DRX |
Intel Corporation |
R2-2205913 |
Open Issues on Signaling for Unicast DRX Configuration |
InterDigital |
R2-2205914 |
Handling DRX Following DCR Message |
InterDigital, Ericsson, Apple |
R2-2206136 |
[H660][V402][V403] Discussion on actions related to reception of UEAssistanceInformationSidelink message |
Huawei, HiSilicon |
R2-2206137 |
[H663] [Z679] [X202] Discussion on implementation of RX UE reporting information related to SL DRX |
Huawei, HiSilicon |
6.15.2.2 |
Configuration aspects |
|
R2-2204579 |
Discussion on DRX left issues for configuration aspects |
OPPO |
R2-2204639 |
Discussion on Tx profile implementation [O074] |
OPPO |
R2-2204640 |
Correction on [O027, O028, O030, O031, O034-O046] |
OPPO |
R2-2204863 |
Discussion on TX profile for broadcast and groupcast |
Huawei, HiSilicon |
R2-2204953 |
Issues corresponding to TX Profile |
CATT |
R2-2205098 |
Discussion on Sidelink UE information |
ZTE Corporation, Sanechips |
R2-2205099 |
Discussion on SL DRX remaining issues for IE design |
ZTE Corporation, Sanechips |
R2-2205100 |
Discussion on TX profile issues for SL DRX |
ZTE Corporation, Sanechips |
R2-2205101 |
(draft)Reply LS to SA2 on Tx Profile |
ZTE Corporation, Sanechips |
R2-2205117 |
remaining issues related to the TX profile |
LG Electronics France |
R2-2205175 |
Discussion on SA2 LS (S2-2203595) |
Ericsson |
R2-2205176 |
Configuration aspects of SL DRX |
Ericsson |
R2-2205183 |
Correction on RIL issue E042 |
Ericsson |
R2-2205184 |
Correction on RIL issue E046 |
Ericsson |
R2-2205185 |
Correction on RIL issue E047 |
Ericsson |
R2-2205262 |
Discussion on SA2 reply LS about TX profile associated with L2 ID(s) |
vivo |
R2-2205265 |
Draft reply LS to SA2 on TX profile associated with L2 ID(s) |
vivo |
R2-2205316 |
[X209] Discussion on preconfigured GC/BC SL DRX usage |
Xiaomi |
R2-2205318 |
[X210] Discussion on GC/BC sidelink DRX operation in partial coverage |
Xiaomi |
R2-2205335 |
Reply LS to SA2 on Tx Profile |
LG Electronics France |
R2-2205537 |
Preferred DRX configuration |
Samsung |
R2-2205538 |
TX profile for GC/BC |
Samsung |
R2-2205620 |
[B200][B201][B202][B203]Some correction for SL DRX Configuration |
Lenovo |
R2-2205642 |
[A914][A918][A919] Discussion on corrections of IUC Scheme 1 configurations in RRC |
Apple |
R2-2205643 |
[Draft] LS on RRC parameters for IUC Scheme 1 |
Apple |
R2-2205644 |
[A904][A905][V380] Discussion on RRC configuration for power-saving resource pools |
Apple |
R2-2205707 |
Discussion on Configuration Aspects |
Qualcomm India Pvt Ltd |
R2-2206048 |
On corrections of TX UE reporting reject related to [H654] |
Huawei, HiSilicon |
R2-2206079 |
(draft)Reply LS to SA2 on Tx Profile |
ZTE Corporation, Sanechips |
6.15.2.3 |
User plane aspects |
|
R2-2204552 |
Clarification on resource re-selection for pre-empted resource with SL DRX |
SHARP Corporation |
R2-2204574 |
Correction on user plane aspects for SL DRX |
OPPO |
R2-2204575 |
Miscellaneous correction on user plane aspects for SL DRX |
OPPO |
R2-2204580 |
Discussion on DRX left issues for user plane aspect |
OPPO |
R2-2204642 |
Correction on [O069, O096, O097] |
OPPO |
R2-2204779 |
Correction on user plane aspects for SL DRX (Rapporteur CR) |
LG Electronics France |
R2-2204781 |
Correction on user plane aspects for SL DRX |
LG Electronics France |
R2-2204782 |
Discussion on remaining issues for user plane aspect |
LG Electronics France |
R2-2204783 |
Discussion on remaining issues for user plane aspect |
LG Electronics France |
R2-2204864 |
Further consideration on SL DRX with TP for MAC spec corrections |
Huawei, HiSilicon |
R2-2204865 |
Clarification on Uu DRX for SL communication |
Huawei, HiSilicon |
R2-2204922 |
Miscellaneous correction on TS 38.321 for SL DRX |
Huawei, HiSilicon |
R2-2204946 |
Combination of SL DRX, Discovery and relay-related Communication |
CATT |
R2-2204947 |
Discussion on the SL DRX Inactivity Timer Maintenance |
CATT |
R2-2204948 |
Correction on the SL DRX Inactivity Timer Maintenance |
CATT |
R2-2204949 |
Discussion on the SL DRX Retransmission Timer Maintenance |
CATT |
R2-2204950 |
Correction on the SL DRX Retransmission Timer Maintenance |
CATT |
R2-2204951 |
Miscellaneous corrections on SL DRX |
CATT |
R2-2205104 |
Correction on resource pool selection for IUC |
ZTE Corporation, Sanechips |
R2-2205105 |
Discussion on user plane FFS issues for SL DRX |
ZTE Corporation, Sanechips |
R2-2205107 |
Correction on Destination ID index in SL BSR |
ZTE Corporation, Sanechips |
R2-2205136 |
Discussion on SL MAC aspects |
ASUSTeK |
R2-2205180 |
Corrections of 38.321 on TX resource selection |
Ericsson |
R2-2205181 |
Corrections of 38.321 on SL grant reception |
Ericsson |
R2-2205182 |
Corrections of 38.321 on IUC MAC CE |
Ericsson |
R2-2205536 |
MAC open issues |
Samsung |
R2-2205622 |
Aligning Parameter names for UC GC and BC |
Lenovo |
R2-2205833 |
Discussion on active time of SL DRX for the announced periodic transmissions |
Nokia, Nokia Shanghai Bell |
R2-2205910 |
Corrections on HARQ RTT Handling in MAC Specification |
InterDigital, Ericsson, Apple |
R2-2205911 |
Corrections on Inactivity Timer Resetting for Groupcast |
InterDigital |
R2-2205912 |
Corrections on Active Time Definition at the TX UE |
InterDigital |
R2-2206309 |
Summary of [AT118-e][712][V2X/SL] User plane discussion (OPPO) |
OPPO |
6.15.2.4 |
Inter-UE Coordination |
|
R2-2204553 |
Remaining issues on resource selection for Inter-UE coordination |
SHARP Corporation |
R2-2204576 |
Correction on user plane aspects for inter-UE coordination |
OPPO |
R2-2204581 |
Discussion on left issue of inter-UE coordination |
OPPO |
R2-2204780 |
Correction on user plane aspects for Inter-UE Coordination (Rapporteur CR) |
LG Electronics France |
R2-2204784 |
Discussion on remaining issues for Inter-UE Coordination |
LG Electronics France |
R2-2204923 |
Remaining issues on inter-UE coordination MAC CE |
Huawei, HiSilicon |
R2-2204924 |
Discussion on latency bound for inter-UE coordination |
Huawei, HiSilicon |
R2-2204952 |
Open Issues of Inter-UE Coordination |
CATT |
R2-2204968 |
Remaining issues on inter-UE coordination |
Lenovo |
R2-2205103 |
Discussion on inter-UE coordination |
ZTE Corporation, Sanechips |
R2-2205137 |
Correction on inter-UE coordination |
ASUSTeK |
R2-2205141 |
Discussion on need of timer-based latency bound restriction for condition-based scenario |
NEC Corporation |
R2-2205177 |
Remaing issues of inter-UE coordination |
Ericsson |
R2-2205344 |
Further Issues on Collision Avoidance of IUC messages |
Nokia, Nokia Shanghai Bell |
R2-2205366 |
Validity of IUCInformation Messages |
Nokia, Nokia Shanghai Bell |
R2-2205535 |
IUC open issues |
Samsung |
R2-2205604 |
Correction on SL grant selection procedure for inter UE coordination |
Samsung |
R2-2205639 |
Discussion on limit of resource combinations in IUC-info MAC CE |
Apple, Ericsson, InterDigital, vivo |
R2-2205640 |
Discussion on the timers for IUC INFO delivery |
Apple |
R2-2205641 |
Lack of priority information for preferred resource set in IUC INFO |
Apple |
R2-2205703 |
Multiple MAC CE handling and remaining PDB related to inter-UE coordination |
vivo |
R2-2205708 |
Discussion on Inter-UE Coordination |
Qualcomm India Pvt Ltd |
R2-2205791 |
Open issues for Inter-UE coordination |
Intel Corporation |
R2-2205881 |
Enabling unsolicited transmission of IUC |
Nokia, Nokia Shanghai Bell |
R2-2206304 |
Summary of [AT118-e][708][V2X/SL] Inter-UE coordination (Apple) |
Apple |
R2-2206313 |
Phase 2 Summary of [AT118-e][708][V2X/SL] Inter-UE coordination (Apple) |
Apple |
R2-2206314 |
LS on IUC with non-preferred resource set |
RAN2 |
6.15.2.5 |
Power-saving resource allocation |
|
R2-2204565 |
[V380] Discussion on the applicability of power-saving resource allocation to NR SL discovery |
vivo |
R2-2204566 |
[V351] On corrections to NR SL communication procedure using exceptional pool |
vivo |
R2-2204567 |
[V350] Corrections on NR SL communication transmission procedures in mode-2 normal pools |
vivo |
R2-2204568 |
[O092] Clarification on the CBR related default parameters |
vivo |
R2-2204577 |
[O092] Correction on default CBR configuration |
OPPO |
R2-2204582 |
[O092] Discussion on default CBR measurement value |
OPPO |
R2-2204641 |
Correction on [O066, O067] |
OPPO |
R2-2205102 |
correction on exceptional resource pool for power saving |
ZTE Corporation, Sanechips |
R2-2205142 |
Correction on user plane aspects for power saving (Rapporteur CR) |
LG Electronics France |
6.15.3 |
Other |
|
R2-2204588 |
Discussion on Sidelink DRX for Sidelink Relay |
MediaTek Inc., APPLE, OPPO |
R2-2204673 |
Discussion on the need of capability filter |
OPPO |
R2-2205179 |
Issues of SL DRX for L2 U2N relay |
Ericsson |
R2-2205269 |
Corrections on the Sidelink DRX |
NEC Corporation |
R2-2205272 |
Way forward for Sidelink DRX configuration report for Relay purpose |
MediaTek Inc. |
R2-2206047 |
Correction on SL DRX configuration for SL Relay |
MediaTek Inc., Huawei, ZTE, OPPO |
R2-2206305 |
Summary of [709][V2X/SL] SL DRX and L2 relay in Rel-17 (Ericsson) |
Ericsson |
6.16.1.1 |
Organizational |
|
R2-2206429 |
Report from [AT118-e][035][eNPN] Corrections (Nokia) |
Nokia (Rapporteur) |
6.16.1.2 |
CR Rapporteur Resolutions |
|
R2-2205489 |
Corrections for eNPN from RAN2#118 |
Nokia, Nokia Shanghai Bell |
R2-2205490 |
Corrections for eNPN from RAN2#118 |
Nokia, Nokia Shanghai Bell |
R2-2206430 |
Corrections for eNPN from RAN2#118 |
Nokia, Nokia Shanghai Bell |
6.16.3 |
Corrections |
|
R2-2206012 |
[E036][E037] Corrections for eNPN |
Ericsson |
6.17.1.1 |
Organizational |
|
R2-2204429 |
Additional LS response to RAN2 on beam management for multi-TRP (R1-2202942; contact: CATT) |
RAN1 |
R2-2204462 |
Reply LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE (R1-2202810; contact: Intel) |
RAN1 |
R2-2204465 |
LS on feMIMO RRC parameters (R1-2202903; contact: Ericsson) |
RAN1 |
R2-2206359 |
LS response on feMIMO RRC parameters (R1-2205168; contact: Samsung) |
RAN1 |
R2-2206438 |
LS response on TCI state signalling for SRS resource (R1-2205247; contact: OPPO) |
RAN1 |
R2-2206443 |
TCI State Indication for SRS Resource |
Samsung |
R2-2206809 |
LS on RAN1#109-e agreements with RAN2 impact (R1-2205591; contact: Samsung) |
RAN1 |
6.17.1.2 |
CR Rapporteur Resolutions |
|
R2-2205207 |
MAC Corrections on feMIMO |
Samsung |
R2-2205497 |
Correction for feMIMO WI |
Ericsson |
R2-2205499 |
MIMO ASN1 RIL list |
Ericsson |
R2-2206831 |
Correction for feMIMO WI |
Ericsson |
R2-2206838 |
MAC Corrections on feMIMO |
Samsung |
R2-2206881 |
Correction for feMIMO WI |
Ericsson |
6.17.3 |
Corrections |
|
R2-2206577 |
Summary of [AT118-e][075][feMIMO] BFD Resource Handling (Apple) |
Apple |
6.17.3.1 |
RRC centric |
|
R2-2204598 |
Discussion open RRC issues on MPE report and BFR |
OPPO |
R2-2204599 |
Discussion on RILs:F001, F002, V101,V102,H059,H060, I105,V112,V109,I115,Z095 |
OPPO |
R2-2204820 |
Discussion on MPE for ICBM |
vivo |
R2-2204914 |
RRC signaling for BFD-RS set configuration |
Fujitsu |
R2-2204915 |
[F002] Beam failure with iner-cell mTRP |
Fujitsu |
R2-2205385 |
[N019, N020, N102, N123] RRC corrections to FeMIMO |
Nokia, Nokia Shanghai Bell |
R2-2205413 |
Consideration on the SRS TCI state for UnifiedTCIState |
ZTE Corporation,Sanechips |
R2-2205414 |
Further Consideration on [RILZ095] for Enhanced MPE |
ZTE Corporation,Sanechips |
R2-2205421 |
Discussion on Association of PCI index and TCI state |
CATT |
R2-2205789 |
Discussion on [I115], [I116, Z095], [I102] |
Intel Corporation |
R2-2205883 |
RILs and other open issues for feMIMO |
Ericsson |
R2-2205915 |
[H059] Channel measurement resource configuration for mTRP |
Huawei, HiSilicon |
R2-2205916 |
[H060] Inter-cell beam measurement configuration |
Huawei, HiSilicon |
R2-2205920 |
[Z095][I116] MPE RRC configuration |
Huawei, HiSilicon |
R2-2205921 |
[H103] SRS resource usage with unified TCI framework |
Huawei, HiSilicon |
R2-2205922 |
[H102] Replace PUCCH-SRS with IE |
Huawei, HiSilicon |
R2-2206332 |
[N102, N123] Corrections to unified TCI state |
Nokia, Nokia Shanghai Bell |
R2-2206348 |
RILs and other open issues for feMIMO |
Ericsson |
R2-2206354 |
[AT118-e][053][feMIMO] Discussion on H060 |
Ericsson |
R2-2206355 |
Draft LS on TCI state signaling for SRS (OPPO) |
OPPO |
R2-2206356 |
LS on TCI state signaling for SRS (OPPO) |
RAN2 |
R2-2206367 |
Report of [AT118-e][054][feMIMO] N102 N123 Unified TCI state (Nokia) |
Nokia (Rapporteur) |
R2-2206592 |
[AT118-e][076][feMIMO] RRC |
Ericsson |
6.17.3.2 |
MAC centric |
|
R2-2204540 |
Remaining Issue for Truncated Enhanced BFR MAC CE |
Samsung Electronics Co., Ltd |
R2-2204569 |
Miscellaneous corrections to BFD/BFR |
CENC |
R2-2204570 |
Update of explicit BFD-RS set by MAC CE |
CENC |
R2-2204596 |
Discussion open MAC issues MPE report and PHR |
OPPO |
R2-2204597 |
Discussion open MAC issues on SRS and CSI-RS |
OPPO |
R2-2204821 |
Discussion on MAC aspects for feMIMO |
vivo |
R2-2204882 |
Remaining issues on MAC |
LG Electronics Inc. |
R2-2205026 |
Remaining issues on Enhanced PHR MAC CE with enhanced MPE |
Nokia, Nokia Shanghai Bell |
R2-2205123 |
Remaining issues on beam failure with mTRP |
Fujitsu |
R2-2205138 |
Discussion on Power Headroom Reporting for mTRP |
ASUSTeK |
R2-2205204 |
Support of BFD-RS set update MAC CE |
Samsung |
R2-2205205 |
Considerations on Enhanced PHR for multiple TRP MAC CE |
Samsung |
R2-2205206 |
Remaining Corrections for MAC issues |
Samsung |
R2-2205242 |
Remaining issues of feMIMO MAC |
Qualcomm Incorporated |
R2-2205281 |
Remaining issue for MPE reporting |
Sharp |
R2-2205415 |
Further Consideration on new PHR For mTRP PUSCH repetition |
ZTE Corporation,Sanechips |
R2-2205416 |
CR on 38.331 for PHR-Config |
ZTE Corporation,Sanechips |
R2-2205420 |
Discussion on Remaining MAC Open Issues |
CATT |
R2-2205674 |
MAC CE for SRS TCI indication |
Apple |
R2-2205675 |
Explicit BFD-RS configuration and indication |
Apple |
R2-2205676 |
mTRP PHR report procedure |
Apple |
R2-2205837 |
Miscellaneous BFR corrections |
Nokia, Nokia Shanghai Bell |
R2-2205838 |
SpCell BFR with multiple BFD-RS sets |
Nokia, Nokia Shanghai Bell |
R2-2205917 |
MAC issues on MPE, mTRP PHR and BFR |
Huawei, HiSilicon |
R2-2205918 |
Discussion on the unified TCI framework related MAC CEs |
Huawei, HiSilicon |
R2-2205919 |
SP-SRS resource set activation by MAC CE |
Huawei, HiSilicon |
R2-2205960 |
Reporting procedure for multi-TRP PHR |
InterDigital |
R2-2206563 |
Summary of [AT118-e] [077] [feMIMO] MAC (Samsung) |
Samsung |
6.18.1 |
Common signalling framework |
|
R2-2205469 |
[C153] The extension solution with bit string for FeatureCombination |
CATT |
R2-2205677 |
Clarification on the RACH partition selection (RIL A022) |
Apple |
R2-2206105 |
Feature extension without using extension marker |
LG Electronics Inc. |
R2-2206126 |
Miscellaneous corrections to RRC specifications for RACH partitioning (RIL: H538, H900, H901, H902) |
Huawei, HiSilicon |
R2-2206127 |
Corrections on handling of per feature combination parameters (RIL: H535, H536, H542, H903, H904) |
Huawei, HiSilicon |
R2-2206221 |
Summary of control plane issues |
Ericsson |
R2-2206431 |
Correction for features applicable to RACCH partitioning |
Ericsson |
R2-2206432 |
Report of [AT118-e][507][RA Part] CP open issues (Ericsson) |
Ericsson |
R2-2206433 |
RICS RIL extract list |
Ericsson |
R2-2206707 |
Correction for features applicable to RACCH partitioning |
Ericsson |
R2-2206708 |
Phase2, CR review - Report from [AT118-e][507][RA Part] CP open issues and CR 38.331 (Ericsson) |
Ericsson |
R2-2206839 |
Correction for features applicable to RACH partitioning |
Ericsson |
6.18.2 |
Common aspects of RACH procedure |
|
R2-2205470 |
Consideration on UP Remaining Issues of RACH common |
CATT |
R2-2205486 |
Correction on fallback cases from CFRA to CBRA for RedCap UE |
LG Electronics Inc. |
R2-2205553 |
MAC Corrections for RACH partitioning |
ZTE Corporation (rapporteur) |
R2-2205839 |
Introduction of RACH partitioning |
Nokia, Nokia Shanghai Bell |
R2-2205840 |
RACH partitioning MAC issues |
Nokia, Nokia Shanghai Bell |
R2-2205876 |
Feature Prioritization for RACH Partitioning |
Ericsson |
R2-2205941 |
Various corrections to MAC spec for RACH partitioning |
Huawei, HiSilicon |
R2-2205942 |
Correction to RACH procedure with SDT applicability |
Huawei, HiSilicon |
R2-2206482 |
AT118-e][508][RA Part] UP open issues and CR 38.321 (ZTE) - Report |
ZTE |
R2-2206484 |
MAC Corrections for RACH partitioning |
ZTE Corporation (rapporteur), LG Electronics Inc. |
R2-2206820 |
Introduction of RACH partitioning |
Nokia, Nokia Shanghai Bell |
R2-2206879 |
Introduction of RACH partitioning |
Nokia, Nokia Shanghai Bell |
6.19.1 |
Organizational |
|
R2-2204444 |
Reply LS on Maximum duration for DMRS bundling (R4-2206537; contact: Qualcomm) |
RAN4 |
R2-2204463 |
Reply LS on UL BWP with PRACH resources only for RACH with Msg3 repetition (R1-2202829; contact: ZTE) |
RAN1 |
R2-2204469 |
Reply LS on Stage 2 description for Coverage Enhancements (R1-2202867; contact: China Telecom) |
RAN1 |
R2-2204505 |
Reply LS on Length of Maximum duration (R4-2206580; contact: China Telecom) |
RAN4 |
R2-2205069 |
Report of [Pre118-e][103][CovEnh] 38331 CR and rapporteur resolutions (Huawei) |
Huawei, HiSilicon |
R2-2206768 |
Reply LS to RAN1/RAN2 on DMRS bundling (R4-2211225; contact: MediaTek) |
RAN4 |
6.19.1.2 |
Rapporteur CRs |
|
R2-2205070 |
Correction for NR coverage enhancements (CR rapporteur) |
Huawei, HiSilicon |
R2-2206410 |
Correction for NR coverage enhancements |
Huawei, HiSilicon |
R2-2206411 |
Correction for NR coverage enhancements |
China Telecom, OPPO, Nokia, Nokia Shanghai Bell |
R2-2206412 |
Correction for NR coverage enhancements |
ZTE Corporation, OPPO, Huawei |
R2-2206776 |
Corrections for NR coverage enhancements |
ZTE Corporation, OPPO, Huawei |
6.19.2 |
General |
|
R2-2204726 |
Stage-2 correction on CE |
OPPO |
R2-2204739 |
Correction to 38.321 on redundancy version for Msg3 repetition |
OPPO |
R2-2204837 |
Discussion on CFRA PUSCH with Repetition |
vivo |
R2-2205067 |
Clarification on Msg3 repetition RV determination to MAC spec |
Huawei, HiSilicon |
R2-2205068 |
Discussion on the leftover issues for CE-specific RACH |
Huawei, HiSilicon |
R2-2205841 |
CE RACH only BWP handling |
Nokia, Nokia Shanghai Bell |
R2-2205842 |
Corrections on MSG3 repetition |
Nokia, Nokia Shanghai Bell |
R2-2205851 |
Further issues on coverage enhancements |
Ericsson |
R2-2205852 |
On CFRA Msg3 repetitions |
Ericsson |
R2-2206034 |
On BWP configured with RACH resources only for Msg3 repetition |
Qualcomm Incorporated |
R2-2206193 |
Report of [AT118-e][103][CovEnh] RRC CR (Huawei) |
Huawei, HiSilicon |
R2-2206220 |
Report of [AT118-e][103][CovEnh] RRC CR (Huawei) - second round |
Huawei, HiSilicon |
R2-2206584 |
Summary of [AT118-e][117][ CovEnh] Stage-2 CR (China Telecom) |
China Telecom |
R2-2206665 |
[AT117-e][118][CovEnh] MAC CR (ZTE) |
ZTE Corporation |
6.20.1 |
Organizational |
|
R2-2204852 |
Correction of RACH preamble lengths for FR2-2 |
Qualcomm Incorporated |
R2-2204869 |
Correction to Stage 2 spec for Ext71GHz |
Huawei, HiSilicon |
R2-2205188 |
Correction of RRC CR for 71 GHz |
Ericsson |
R2-2205189 |
RIL issues of RRC CR correction for 71 GHz |
Ericsson |
R2-2205195 |
Correction of 38.300 |
Ericsson |
R2-2206176 |
Report of [AT118-e][210][71 GHz] RRC corrections (Ericsson) |
Ericsson |
R2-2206177 |
Correction of RRC CR for 71 GHz |
Ericsson |
R2-2206178 |
[AT118-e][211][71 GHz] Stage-2 corrections for 71 GHz (Qualcomm) |
Qualcomm Incorporated |
R2-2206364 |
LTE RRC Corrections to 71 GHz |
Ericsson |
R2-2206374 |
Report of [AT118-e][211][71 GHz] Stage-2 corrections for 71 GHz (Qualcomm) |
Qualcomm |
R2-2206448 |
Correction of LBT access mode |
Qualcomm Incorporated, Huawei |
R2-2206552 |
LS to RAN2 on RRC parameter updates for NR up to 71GHz (R1-2205380; contact: Qualcomm) |
RAN1 |
R2-2206687 |
Stage-2 corrections for 71 GHz |
Qualcomm Incorporated (Rapporteur) |
R2-2206764 |
LS on CCA configurations of neighbour cells (R4-2211171; contact: Nokia) |
RAN4 |
R2-2206792 |
Correction of RRC CR for 71 GHz |
Ericsson |
R2-2206793 |
LTE RRC Corrections to 71 GHz |
Ericsson |
R2-2206808 |
LS on TCI assumption for RSSI measurement for FR2-2 (R1-2205582; contact: Qualcomm) |
RAN1 |
R2-2206851 |
RRC correction CR for 71 GHz |
Ericsson |
R2-2206852 |
Overheating assistance info for FR2-2 in (NG)EN-DC - RIL E801 |
Ericsson |
R2-2206857 |
RRC correction CR for 71 GHz |
Ericsson |
R2-2206858 |
RRC correction CR for 71 GHz |
Ericsson |
6.20.2 |
Control plane corrections |
|
R2-2204871 |
Correction to periodicityAndOffset for Ext 71GHz [H707] |
Huawei, HiSilicon |
R2-2204872 |
Discussion on overheating assistance report for SCG in EN-DC |
Huawei, HiSilicon |
R2-2205050 |
[S626] Clarification on drx-HARQ-RTT-TimerDL/UL |
Samsung |
R2-2205051 |
[E048] Overheating assistance information for FR2-2 in (NG)EN-DC |
Samsung |
R2-2205052 |
[E048] Overheating information for FR2-2 in (NG)EN-DC (38.331) |
Samsung |
R2-2205053 |
[E801] Overheating information for FR2-2 in (NG)EN-DC (36.331) |
Samsung |
R2-2205190 |
Correction on RIL issue E801 |
Ericsson |
R2-2205191 |
Correction on RIL issue E049 |
Ericsson |
R2-2205192 |
Correction on RIL issue E134 |
Ericsson |
R2-2205193 |
Correction on RIL issue E135 |
Ericsson |
R2-2205194 |
Correction on RIL issue E136 |
Ericsson |
R2-2205554 |
Control plane issues for NR operation above 71 GHz |
ZTE Corporation, Sanechips |
6.20.3 |
User plane corrections |
|
R2-2205239 |
Discussion and related TP on necessary update of Rel-16 LBT |
CATT |
R2-2205555 |
User Plane Issues for NR operation above 71 GHz |
ZTE Corporation, Sanechips |
6.20.4 |
UE capabilities |
|
R2-2204870 |
Correction to 38.306 for Ext71GHz |
Huawei, HiSilicon |
R2-2205792 |
Remaining UE capabilities on NR operation for upto 71GHz |
Intel Corporation |
R2-2205793 |
Further updates for 71GHz UE capabilities (TS38.306) |
Intel Corporation |
R2-2205794 |
Further updates for 71GHz UE capabilities (TS38.331) |
Intel Corporation |
R2-2206179 |
Report of [AT118-e][212][71 GHz] 71 GHz UE capability corrections (Intel) |
Intel Corporation |
R2-2206180 |
Further updates for 71GHz UE capabilities (TS38.306) |
Intel Corporation |
R2-2206181 |
Further updates for 71GHz UE capabilities (TS38.331) |
Intel Corporation |
6.21.1 |
TEI proposals initiated by other groups |
|
R2-2204494 |
Response LS on Conditional Handover with SCG configuration scenarios (R3-222840; contact: Nokia) |
RAN3 |
R2-2204935 |
Discussion on remaining issues on CHO including SCG configuration |
Intel Corporation |
R2-2205282 |
Discussion on CHO with target SCG |
MediaTek Inc. |
R2-2205472 |
Discussion on CHO with SCG configuration |
CATT, Huawei, ZTE, China Unicom, China Telecommunications, CMCC, Ericsson |
R2-2205473 |
Support of CHO with SCG configuration - 36331 [CHOwithDCkept] |
CATT, Huawei, ZTE, China Unicom, China Telecommunications, CMCC, Ericsson |
R2-2205474 |
Support of CHO with SCG configuration - 38331 [CHOwithDCkept] |
CATT, Huawei, ZTE, China Unicom, China Telecommunications, CMCC, Ericsson |
R2-2205475 |
Support of CHO with SCG configuration - 37340 [CHOwithDCkept] |
CATT, Huawei, ZTE, China Unicom, China Telecommunications, Nokia, Nokia Shanghai Bell, CMCC, Ericsson |
R2-2205532 |
Supporting CHO with SCG configuration in 38.331 |
Nokia, Nokia Shanghai Bell |
R2-2206004 |
CHO configuration with SCG |
Qualcomm Incorporated |
R2-2206005 |
CHO configuration with SCG |
Qualcomm Incorporated |
R2-2206456 |
Introduction UE capability for CHO with SCG configuration |
MediaTek Inc. |
R2-2206457 |
Introduction UE capability for CHO with SCG configuration |
MediaTek Inc. |
R2-2206599 |
Report of [AT118-e][036][TEI17] CHO with SCG (CATT) |
CATT |
R2-2206600 |
Support of CHO with SCG configuration - 36331 [CHOwithDCkept] |
CATT, Huawei, ZTE, China Unicom, China Telecommunications, Nokia, Nokia Shanghai Bell, CMCC, Ericsson |
R2-2206601 |
Support of CHO with SCG configuration - 38331 [CHOwithDCkept] |
CATT, Huawei, ZTE, China Unicom, China Telecommunications, Nokia, Nokia Shanghai Bell, CMCC, Ericsson |
R2-2206602 |
Support of CHO with SCG configuration - 37340 [CHOwithDCkept] |
CATT, Huawei, ZTE, China Unicom, China Telecommunications, Nokia, Nokia Shanghai Bell, CMCC, Ericsson |
R2-2206709 |
Introduction UE capability for CHO with SCG configuration [CHOwithDCkept] |
MediaTek Inc. |
R2-2206710 |
Introduction UE capability for CHO with SCG configuration [CHOwithDCkept] |
MediaTek Inc. |
R2-2206762 |
LS on timing advance (TADV) report mapping for NR UL E-CID positioning (R4-2211167; contact: Ericsson) |
RAN4 |
R2-2206766 |
LS on Incorrect PMI Reporting (R4-2211204; contact: Apple) |
RAN4 |
6.21.2 |
TEI proposals initiated by RAN2 |
|
R2-2204524 |
Reply LS on EPS fallback enhancements (S2-2203590; contact: Qualcomm) |
SA2 |
R2-2204622 |
Periodic SRS in SCell dormant BWP |
Qualcomm Incorporated, ZTE Corporation, Futurewei |
R2-2204853 |
Leaving indication for CHO execution |
Qualcomm Incorporated |
R2-2205034 |
Discussion on remote access issue |
CMCC |
R2-2205054 |
Early measurement for EPS Fallback |
vivo, China Telecom, CMCC, SoftBank, China Unicom, Vodafone, Ericsson |
R2-2205055 |
38331 CR for Early measurement for EPS Fallback |
vivo, China Telecom, CMCC, SoftBank, China Unicom, Vodafone |
R2-2205056 |
Discussion on the identification of remote access UE |
vivo |
R2-2205519 |
Indication of RRC Segmentation capability for UE capability report |
Huawei, HiSilicon, Apple, BT, CATT, CMCC, China Unicom, Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, NTT DOCOMO INC., Qualcomm Incorporated, Vodafone, ZTE Corporation, Sanechips |
R2-2205566 |
Inclusion of the CSI reports in MDT framework |
Nokia, Nokia Shanghai Bell |
R2-2205664 |
Priority based inter-freq measurement reporting |
Apple |
R2-2205679 |
SDAP end-marker in RLC UM |
Apple, Futurewei, Spreadtrum, FGI, Asia Pacific Telecom, T-Mobile USA |
R2-2205832 |
On inter-frequency measurement configuration and reporting enhancements |
BT Plc., Ericsson, Vodafone, T-Mobile USA, Qualcomm |
R2-2205845 |
Remaining details for high-precision GNSS reporting |
ESA, Ericsson, Deutsche Telekom, T-Mobile USA, Swift Navigation, Hexagon |
R2-2205849 |
Enhancements for CA with different numerologies |
Qualcomm Incorporated |
R2-2205882 |
Flexible gNB ID length |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS |
R2-2205884 |
Latency Reduction during EPS Handover Fallback |
Vodafone GmbH |
R2-2205997 |
Correction to DRX operation with bundling controlled in the DCI |
Ericsson, Nokia, T-Mobile USA, Verizon, Docomo |
R2-2206118 |
Latency Reduction during EPS Handover Fallback |
Vodafone GmbH |
R2-2206144 |
Inclusion of the CSI reports in MDT framework |
Nokia, Nokia Shanghai Bell, Verizon, Deutsche Telekom |
R2-2206329 |
Remaining details for high-precision GNSS reporting |
ESA, Ericsson, Deutsche Telekom, T-Mobile USA, Swift Navigation, Hexagon, MediaTek Inc., u-blox |
R2-2206334 |
Flexible gNB ID length |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, UE Cellular |
R2-2206349 |
Indication of RRC Segmentation capability for UE capability report |
Huawei, HiSilicon, BT, CATT, CMCC, China Unicom, Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, NTT DOCOMO INC., Qualcomm Incorporated, Vodafone, ZTE Corporation, Sanechips |
R2-2206395 |
[AT118-e][628][POS] NMEA GGA string for HA-GNSS reporting (Ericsson) |
Ericsson |
R2-2206444 |
NMEA GGA sentence info in high accuracy GNSS location estimates [HR-GNSS-NMEA] |
ESA, Ericsson, Deutsche Telecom, T-Mobile USA, Swift Navigation, Hexagon, MediaTek Inc., u-blox |
R2-2206492 |
LS on Flexible Global RAN Node ID (R3-223883; contact: Ericsson) |
RAN3 |
R2-2206539 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular |
R2-2206540 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular |
R2-2206541 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular |
R2-2206542 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular |
R2-2206543 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular |
R2-2206544 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular |
R2-2206594 |
[AT118-e][081][TEI17] Early Measurements for EPS fallback |
vivo |
R2-2206595 |
38331 CR for Early measurement for EPS Fallback |
vivo, China Telecom, CMCC, SoftBank, China Unicom, Vodafone |
R2-2206596 |
Indication on EPS fallback frequency |
vivo, China Telecom, CMCC, SoftBank, China Unicom, Vodafone |
R2-2206649 |
Summary of [AT118-e][082][TEI17] RRC Segmentation capability for UE capability report |
Huawei, HiSilicon |
R2-2206673 |
Reply LS on Flexible Global RAN Node ID |
RAN2 |
R2-2206689 |
Reply LS on Flexible Global RAN Node ID |
RAN2 |
R2-2206713 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular, Deutsche Telekom, Nokia |
R2-2206714 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular, Deutsche Telekom, Nokia |
R2-2206715 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular, Deutsche Telekom, Nokia |
R2-2206716 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular, Deutsche Telekom, Nokia |
R2-2206717 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular, Deutsche Telekom, Nokia |
R2-2206718 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular, Deutsche Telekom, Nokia |
R2-2206778 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206779 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206780 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206781 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206782 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206783 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206784 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206785 |
Introduction of uplink RRC Segmentation capability |
Huawei, HiSilicon |
R2-2206795 |
Reply LS on EPS fallback enhancements (C1-223535; contact: Qualcomm) |
CT1 |
R2-2206824 |
[Post118-e][081][TEI17] Early Measurements for EPS fallback (vivo) |
vivo |
R2-2206825 |
Early Measurements for EPS fallback [IdleMeaEPSFB] |
vivo, China Telecom, CMCC, SoftBank, China Unicom, Vodafone, ZTE |
R2-2206841 |
NMEA GGA sentence info in high accuracy GNSS location estimates [HR-GNSS-NMEA] |
ESA, Ericsson, Deutsche Telecom, T-Mobile USA, Swift Navigation, Hexagon, MediaTek Inc., u-blox |
R2-2206850 |
NMEA GGA sentence info in high accuracy GNSS location estimates [HA-GNSS-NMEA] |
ESA, Ericsson, Deutsche Telekom, T-Mobile USA, Swift Navigation, Hexagon, MediaTek Inc., u-blox |
R2-2206874 |
Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
Ericsson, Verizon, China Telecom, Bell Mobility, Samsung, Rogers, TELUS, Telecom Italia, T-Mobile USA, US Cellular, Deutsche Telekom, Nokia |
R2-2206880 |
Early Measurements for EPS fallback [IdleMeaEPSFB] |
vivo, China Telecom, CMCC, SoftBank, China Unicom, Vodafone, ZTE |
6.21.3 |
Corrections |
|
R2-2205417 |
Extension of the timeDomainAllocation for CG type 1 with typeB repetition |
ZTE Corporation,Huawei, China Telecom, Sanechips |
R2-2205418 |
Addition of UE capability of extension of TDRA indication for Configured UL Grant type 1 |
ZTE Corporation,Huawei, China Telecom, Sanechips |
R2-2205563 |
Discussion on RRC status after reception of RRCRelease |
Huawei, HiSilicon |
R2-2205647 |
Correction on A901 for SI scheduling offset |
Apple |
R2-2206633 |
Extension of the time domain resource allocation indicator for CG type 1 with typeB repetition |
ZTE Corporation,Huawei, China Telecom, Sanechips |
R2-2206634 |
Correction on the UE capability of extension of TDRA indication for Configured UL Grant type 1 |
ZTE Corporation, Huawei, China Telecom, Sanechips |
R2-2206652 |
Report of [AT118-e][037][NR17] TEI Correction (ZTE) |
ZTE Corporation (Rapporteur) |
6.22.1.1 |
Organizational |
|
R2-2204474 |
LS on R17 MG enhancement - NCSG (R4-2206890; contact: Apple) |
RAN4 |
R2-2206746 |
LS on R17 NR MG enhancements – Pre-configured MG (R4-2210587; contact: OPPO, Intel) |
RAN4 |
R2-2206747 |
LS on R17 MG enhancement - NCSG (R4-2210589; contact: Apple) |
RAN4 |
6.22.1.2 |
CR Rapporteur Resolutions |
|
R2-2205220 |
Discussion on MGE RIL issues |
MediaTek Inc. |
R2-2205223 |
Clarification and correction for measurement gap enhancement features |
MediaTek Inc. |
R2-2206455 |
Clarification and correction for measurement gap enhancement features |
MediaTek Inc. |
6.22.3.1 |
Preconfigured Measurement Gaps |
|
R2-2204543 |
Discussion on gap activation triggered by PRS measurement |
ZTE Corporation, Sanechips |
R2-2204822 |
Discussion on per-configured measurement gap |
vivo |
R2-2205241 |
[H650][H651][M602][M603] Correction on pre-configured MG |
MediaTek Inc. |
R2-2205267 |
[M607] Discussion on activation of pre-configured gap for PRS measurement |
MediaTek Inc. |
R2-2205291 |
Discussion on pre-config MG for positioning |
Huawei, HiSilicon |
R2-2205292 |
[H650][M604] Discussion on deactivatedMeasGapList and conditional presence of gap ID |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
R2-2205378 |
Resolving FFS on pre-MG |
Samsung |
R2-2205726 |
[N126][N127] On Pre-configured Measurement Gaps FFS issue for PRS measurement |
Nokia, Nokia Shanghai Bell |
R2-2206014 |
Pre-configured measurement gaps |
Ericsson |
R2-2206401 |
Report of [AT118-e][069][MGE] Pre-configured MG (Intel) |
Intel |
6.22.3.2 |
Concurrent Measurement Gaps |
|
R2-2204823 |
Discussion on concurrent measurement gaps |
vivo |
R2-2204976 |
[C101][C100] Consideration on Concurrent Measurement Gaps |
CATT |
R2-2205227 |
Discussion on Concurrent MG |
Xiaomi Communications |
R2-2205229 |
[E033][E034][H652][M604][M605][M606] Correction on ToAddModList and Gap ID for multiple gap configurations |
MediaTek Inc. |
R2-2205376 |
[S651] Including one gap without measGapId in concurrent gaps |
Samsung |
R2-2205377 |
Resolving FFS on Conditional Presence of GapId |
Samsung |
R2-2206013 |
[E033][E034] On the MGE structure |
Ericsson |
R2-2206015 |
On [E030] and further concurrent MG aspects |
Ericsson |
R2-2206113 |
[H653] Corrections on associatedMeasGapSSB and associatedMeasGapCSIRS |
Huawei, HiSilicon |
R2-2206453 |
Report of [AT118-e][059][MGE] Concurrent MG (MediaTek) |
MediaTek Inc. |
R2-2206454 |
[E033][E034][H652][M604][M605][M606] Correction on ToAddModList and Gap ID for multiple gap configurations |
MediaTek Inc. |
6.22.3.3 |
Network Configured Small Gaps |
|
R2-2204545 |
[Z142] Correction on deriveSSB-IndexFromCellInter field |
ZTE Corporation, Sanechips |
R2-2205692 |
Discussion on the supported combinations of NCSG and legacy gaps |
Huawei, HiSilicon |
R2-2205727 |
[Z142]On relationship between deriveSSB-IndexFromCellInter and deriveSSB-IndexFromCell |
Nokia, Nokia Shanghai Bell |
R2-2206070 |
[H804][H805][H806] Corrections on mgta and mgl |
Huawei, HiSilicon |
R2-2206071 |
[H807] Clarification on ncsgInd |
Huawei, HiSilicon |
R2-2206491 |
[H804][H805][H806] Corrections on mgta and mgl |
Huawei, HiSilicon |
R2-2206531 |
Summary of [AT118-e][061][MGE] Network Configured Small Gaps (Apple) |
Apple |
R2-2206557 |
[H807] Correction to ncsg-MeasGap-r17 |
Huawei, HiSilicon |
R2-2206677 |
Correction on deriveSSB-IndexFromCellInter field description |
Nokia, Nokia Shanghai Bell |
6.22.4 |
UE capabilities |
|
R2-2204824 |
Discussion on NCSG |
vivo |
R2-2204825 |
Discussion on capability for MG enhancement |
vivo |
R2-2205293 |
Discussion on UE capability for dynamically reporting the NCSG requirement |
Huawei, HiSilicon |
R2-2205379 |
Resolving FFS on UE capabilities for MGE |
Samsung |
R2-2205728 |
On MGE UE capabilities left issues |
Nokia, Nokia Shanghai Bell |
R2-2205935 |
Open issues for MGE |
Intel Corporation |
R2-2206007 |
Per-UE Concurrent Gaps Capability |
Qualcomm Incorporated |
R2-2206008 |
Per-UE Concurrent Gaps Capability |
Qualcomm Incorporated |
R2-2206009 |
Preconfigured gap capability |
Qualcomm Incorporated |
R2-2206010 |
Preconfigured gap capability |
Qualcomm Incorporated |
R2-2206016 |
UE capabilities for MGE |
Ericsson |
R2-2206357 |
Discussion on UE capability for dynamically reporting the NCSG requirement |
Huawei, HiSilicon |
R2-2206402 |
Summary document for UE capability |
Intel |
R2-2206424 |
UE capability bit to support 2 per-UE gap only for UE concurrent gap |
Intel |
R2-2206425 |
UE capability bit to support 2 per-UE gap only for UE concurrent gap |
Intel |
R2-2206621 |
UE capability bit to support 2 per-UE gap only for UE concurrent gap |
Intel |
R2-2206642 |
UE capability bit to support 2 per-UE gap only for UE concurrent gap |
Intel |
R2-2206643 |
Correction on NCSG Capability |
MediaTek Inc. |
R2-2206644 |
Correction on NCSG Capability |
MediaTek Inc. |
R2-2206680 |
Way forward for Rel17 UE not capable of NCSG |
Intel Corporation |
6.23.1 |
Organizational |
|
R2-2204492 |
Reply LS on NR UDC for CU-CP/UP splitting scenario (R3-222724; contact: CATT) |
RAN3 |
6.23.2 |
Corrections |
|
R2-2205071 |
Discussion on UE capability of buffer size and UE autonomous buffer reset |
Huawei, HiSilicon |
R2-2205719 |
Clarification on UDC packet |
Samsung |
R2-2206096 |
Correction for NR UDC in 38.331 (CR Rapporteur) |
CATT |
R2-2206148 |
Corrections to UDC |
Lenovo |
R2-2206149 |
Corrections to UDC |
Lenovo |
R2-2206426 |
Report of [AT118-e][038][UDC] UDC Corrections (CATT) - Phase 1 |
CATT |
R2-2206628 |
Corrections to UDC |
Lenovo |
R2-2206666 |
Correction for NR UDC in 38.331 |
CATT |
R2-2206669 |
Corrections on UDC capability |
Huawei, HiSilicon |
R2-2206670 |
Corrections on UDC capability |
Huawei, HiSilicon |
6.24.1 |
RAN4 led Items |
|
R2-2204432 |
Reply LS on interruption for PUCCH SCell activation in invalid TA case (R1-2202599; contact: MediaTek) |
RAN1 |
R2-2204443 |
Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure (R1-2202778; contact: Huawei) |
RAN1 |
R2-2204459 |
LS On Canada band n77 (R4-2206568; contact: Telus) |
RAN4 |
R2-2204473 |
LS on release independent for FR1 HST RRM enhancement (R4-2206846; contact: CMCC) |
RAN4 |
R2-2204488 |
LS on release independent for FR1 HST demodulation (R4-2207195; contact: CMCC) |
RAN4 |
R2-2204489 |
LS on UE capability and network assistant signalling for CRS interference mitigation in scenarios with overlapping spectrum for LTE and NR (R4-2207238; contact: China Telecom) |
RAN4 |
R2-2204501 |
LS on clarification of dualPA-Architecture capability (R4-2206503; contact: OPPO) |
RAN4 |
R2-2204506 |
Reply LS on DC location for >2CC (R4-2206602; contact: Qualcomm) |
RAN4 |
R2-2204507 |
LS to RAN2 on UL gap in FR2 RF enhancement (R4-2206608; contact: Apple) |
RAN4 |
R2-2204600 |
CR to Clarification of PUCCH group definition |
OPPO |
R2-2204601 |
Discusson on concept of PUCCH group |
OPPO |
R2-2204629 |
Discussion on R4 LS on dual-PA architecture clarification |
OPPO |
R2-2204630 |
Extension of dual-PA architecture capability |
OPPO |
R2-2204631 |
Extension of dual-PA architecture capability |
OPPO |
R2-2204850 |
Introduction of FR2 FBG2 CA BW classes |
Nokia, Nokia Shanghai Bell, , Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications |
R2-2204851 |
Introduction of FR2 FBG2 CA BW classes |
Nokia, Nokia Shanghai BellNokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications |
R2-2204854 |
Reply LS on release independence aspects of newly introduced FR2 CA BW Classes and CBM/IBM UE capability |
Nokia, Nokia Shanghai Bell |
R2-2204889 |
CR on the CBM/IBM reporting-38331 |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
R2-2204890 |
CR on the CBM/IBM reporting-38306 |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
R2-2204980 |
CR to TS 38.306 on UE capability for Rel-17 CRS interference mitigation |
China Telecom, Huawei, HiSilicon |
R2-2204981 |
CR to TS 38.331 on UE capability for Rel-17 CRS interference mitigation |
China Telecom, Huawei, HiSilicon |
R2-2204982 |
CR to TS 38.331 on Network assistant signalling for Rel-17 CRS interference mitigation |
China Telecom, Huawei, HiSilicon |
R2-2205266 |
Further discussion on DC location reporting for more than 2 CCs |
Qualcomm Incorporated |
R2-2205380 |
Clarification to dualPA-Architecture |
Nokia, Nokia Shanghai Bell |
R2-2205381 |
Clarification to dualPA-Architecture |
Nokia, Nokia Shanghai Bell |
R2-2205382 |
Clarification to dualPA-Architecture |
Nokia, Nokia Shanghai Bell |
R2-2205383 |
Clarification to dualPA-Architecture |
Nokia, Nokia Shanghai Bell |
R2-2205384 |
Clarification to dualPA-Architecture |
Nokia, Nokia Shanghai Bell |
R2-2205386 |
DC location reporting for Rel-17 |
Nokia, Nokia Shanghai Bell |
R2-2205387 |
Introduction of Rel-17 DC location reporting |
Nokia, Nokia Shanghai Bell |
R2-2205388 |
Introduction of network assistance signalling for CRS-IM |
Nokia, Nokia Shanghai Bell |
R2-2205389 |
Introduction of network assistance signalling for CRS-IM |
Nokia, Nokia Shanghai Bell |
R2-2205390 |
UE capabilities for network assistance signalling for CRS-IM |
Nokia, Nokia Shanghai Bell |
R2-2205391 |
UE capabilities for network assistance signalling for CRS-IM |
Nokia, Nokia Shanghai Bell |
R2-2205393 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2205394 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2205395 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2205396 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2205450 |
Discussion on n77 issues |
Xiaomi Communications |
R2-2205514 |
Clarification on DC location reporting for dual PA UE |
Huawei, HiSilicon |
R2-2205515 |
Clarification on DC location reporting for dual PA UE |
Huawei, HiSilicon |
R2-2205516 |
Discussion on dualPA-Architecture capability |
Huawei, HiSilicon |
R2-2205517 |
Discussion on the DC location report for more than 2CCs |
Huawei, HiSilicon |
R2-2205518 |
Introduction of DC location reporting for more than 2CCs |
Huawei, HiSilicon |
R2-2205562 |
Discussion on FR2 new bandwidth class |
Huawei, HiSilicon |
R2-2205659 |
Correction on FR2 UL gap |
Apple |
R2-2205666 |
Summary of [Pre118-e][004][NR17 FR2 UL Gap] 38331 CR and rapporteur resolutions (Apple) |
Apple |
R2-2205667 |
Addressing FR2 UL gap RILs [Z151, Z152, A803, A804, A807, A808] |
Apple |
R2-2205735 |
Introduction of Rel-17 DC location reporting |
Nokia, Nokia Shanghai Bell |
R2-2205870 |
Terminology for n77 extension |
Ericsson |
R2-2205871 |
Terminology for n77 extension |
Ericsson |
R2-2205872 |
Terminology for n77 extension |
Ericsson |
R2-2205873 |
Terminology for n77 extension |
Ericsson |
R2-2205874 |
Terminology for n77 extension |
Ericsson |
R2-2205875 |
Terminology for n77 extension |
Ericsson |
R2-2205980 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2205981 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2205982 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2205983 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2206427 |
Summary of [AT118-e][044][NR17] Dual PA (OPPO) |
OPPO |
R2-2206428 |
LS reply on clarification of dualPA-Architecture capability |
RAN2 |
R2-2206439 |
LS on UE capability and network assistant signalling for CRS interference mitigation in the scenario with overlapping spectrum for LTE and NR with 30kHz SCS (R4-2210435; contact: CMCC) |
RAN4 |
R2-2206461 |
Summary of [AT118-e][041][NR17] FR2 UL gap (Apple) |
Apple |
R2-2206462 |
Correction on FR2 UL gap |
Apple |
R2-2206463 |
Addressing FR2 UL gap RILs [Z151, Z152, A803, A804, A807, A808] |
Apple |
R2-2206488 |
Report from [AT118-e][046][NR17] n77 and DSS (Ericsson) |
Ericsson |
R2-2206522 |
Summary of [AT118-e][043][NR17] CRS interference mitigation (China Telecom) |
China Telecom |
R2-2206523 |
CR to TS 38.306 on UE capability for Rel-17 CRS interference mitigation |
China Telecom, Huawei, HiSilicon |
R2-2206524 |
CR to TS 38.331 on UE capability for Rel-17 CRS interference mitigation |
China Telecom, Huawei, HiSilicon |
R2-2206525 |
CR to TS 38.331 on Network assistant signalling for Rel-17 CRS interference mitigation |
China Telecom, Huawei, HiSilicon |
R2-2206564 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2206565 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2206566 |
Report of [AT118-e][039][NR17] n77 Canada (Nokia) |
Nokia (Rapporteur) |
R2-2206568 |
Offline [AT118-e][042][NR17] FR2 CA BW Classes and CBM/IBM (Nokia) |
Nokia (Rapporteur) |
R2-2206590 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2206591 |
Distinguishing support of band n77 restrictions in Canada |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2206636 |
Report of [AT118-e][040][NR17] PUCCH Group (Huawei) |
Huawei, HiSilicon |
R2-2206637 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2206638 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2206639 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2206640 |
Adding UE capability of CSI reporting cross PUCCH SCell group |
Huawei, HiSilicon |
R2-2206650 |
Introduction of DC location reporting for more than 2CCs |
Huawei, HiSilicon |
R2-2206759 |
LS on DC location for intra-band CA (R4-2210782; contact: vivo) |
RAN4 |
R2-2206763 |
LS on clarification of RACH prioritisation rules between LTE and NR-U (R4-2211170; contact: Ericsson) |
RAN4 |
R2-2206767 |
LS to RAN2 on UL gap in FR2 RF enhancement (R4-2211222; contact: Apple) |
RAN4 |
R2-2206804 |
Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure (R1-2205463; contact: Huawei) |
RAN1 |
R2-2206867 |
Distinguishing support of band n77 restrictions in Canada [n77 Canada] |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2206868 |
Distinguishing support of band n77 restrictions in Canada [n77 Canada] |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2206870 |
Distinguishing support of band n77 restrictions in Canada [n77 Canada] |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
R2-2206871 |
Distinguishing support of band n77 restrictions in Canada [n77 Canada] |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Telus, Bell Canada |
6.24.2 |
RAN1 led Items |
|
R2-2205511 |
Editorial correction for NR dynamic spectrum sharing |
Ericsson |
6.24.3 |
Other |
|
R2-2204510 |
LS on system information extensions for minimization of service interruption (MINT) (C1-223219; contact: Ericsson) |
CT1 |
R2-2204527 |
Reply LS on Reply LS on MINT functionality for Disaster Roaming (S3-220518; contact: LGE) |
SA3 |
R2-2204529 |
LS on MINT functionality for Disaster Roaming (S5-222575; contact: Ericsson) |
SA5 |
R2-2205520 |
Discussion on supporting case A from CT1 on MINT |
Huawei, HiSilicon |
R2-2205618 |
TP to resolve TBD on oneBitApproach for MINT |
LG Electronics France |
R2-2205867 |
Introducing single-bit approach for MINT [MINT] |
Ericsson |
R2-2205868 |
Introducing single-bit approach for MINT [MINT] |
Ericsson |
R2-2205869 |
Remaining issues for MINT |
Ericsson |
R2-2205992 |
Support of of case A from CT1 on MINT |
Huawei, HiSilicon |
R2-2205993 |
Support of of case A from CT1 on MINT |
Huawei, HiSilicon |
R2-2206049 |
Corrections to MINT specification [MINT] |
Lenovo |
R2-2206050 |
Corrections to MINT specification [MINT] |
Lenovo |
R2-2206477 |
Report from [AT118-e][047][NR17] MINT (Ericsson) |
Ericsson |
R2-2206478 |
Introducing single-bit approach for MINT [MINT] |
Ericsson, Lenovo |
R2-2206479 |
Introducing single-bit approach for MINT [MINT] |
Ericsson, Lenovo |
R2-2206480 |
Reply LS on system information extensions for minimization of service interruption (MINT) |
RAN2 |
7.0.1 |
ASN.1 review |
|
R2-2205208 |
Corrections on the general ASN.1 issues |
Samsung |
R2-2205209 |
LTE Rel-17 ASN.1 Review, Class 0 issues |
Samsung |
R2-2205210 |
LTE Rel-17 RIL List |
Samsung |
R2-2205866 |
E806 - Avoiding SIB30, SIB31, and SIB32 in the old SI-scheduling list |
Ericsson |
R2-2206190 |
Corrections on the general ASN.1 issues |
Samsung |
R2-2206360 |
LTE Rel-17 ASN.1 Review, Class 0 issues |
Samsung |
R2-2206361 |
LTE Rel-17 RIL List |
Samsung |
7.0.3 |
Feature Lists and UE capabilities |
|
R2-2204426 |
LS on updated Rel-17 RAN1 UE features list for LTE (R1-2202924; contact: NTT DOCOMO, AT&T) |
RAN1 |
R2-2206471 |
LS on updated Rel-17 RAN1 UE features list for LTE (R1-2205326; contact: NTT DOCOMO, AT&T) |
RAN1 |
7.1.1 |
Organizational |
|
R2-2204421 |
LS on use of CQI table for NB-IoT DL 16QAM (R1-2202880; contact: Huawei) |
RAN1 |
R2-2204423 |
LS on UE capability for 16QAM for NB-IoT (R1-2202893; contact: Qualcomm) |
RAN1 |
R2-2205564 |
Corrections based on ASN.1 review of R17 NB-IoT/eMTC Enhancements |
Qualcomm Incorporated |
R2-2205565 |
Report of ASN.1 R17 Review for NB-IoT/eMTC enhancements |
Qualcomm Incorporated |
R2-2206271 |
Corrections to R17 NB-IoT/eMTC Enhancements |
Qualcomm Incorporated |
R2-2206272 |
Correction to coverage based paging |
Nokia, Nokia Shanghai Bell |
R2-2206745 |
LS reply on UE capability for 16QAM for NB-IoT (R4-2210571; contact: Ericsson) |
RAN4 |
R2-2206861 |
Correction to coverage based paging |
Nokia, Nokia Shanghai Bell |
7.1.2 |
Corrections |
|
R2-2205149 |
Clarification on NPUSCH repetition number for PUR with 16QAM |
ZTE Corporation, Sanechips |
R2-2205162 |
RILZ312, Z313, Z316, Z317, Z318 CEL-based paging |
ZTE Corporation, Sanechips |
R2-2205323 |
RIL H101 : Coverage based paging |
Huawei, HiSilicon |
R2-2205324 |
Correction to coverage based paging |
Huawei, HiSilicon |
R2-2205878 |
RILZ312, Z313, Z316 CEL-based paging |
ZTE Corporation, Sanechips |
R2-2206039 |
RIL H112 (new): 16 QAM DL configuration |
Huawei, HiSilicon |
7.2.1.1 |
Organizational |
|
R2-2204428 |
LS on IoT-NTN TP for TS 36.300 (R1-2202931; contact: MediaTek) |
RAN1 |
R2-2204437 |
LS Response to LS on UE providing Location Information for NB-IoT (S2-2201333; contact: Qualcomm) |
SA2 |
R2-2204451 |
Reply LS on UE providing Location Information for NB-IoT (C1-222100; contact: Apple) |
CT1 |
R2-2204457 |
Reply LS on opens issues for NB-IoT and eMTC support for NTN (S3-220543; contact: Xiaomi) |
SA3 |
R2-2204458 |
Reply LS on security concerns for UE providing Location Information for NB-IoT (S3-220544; contact: Xiaomi) |
SA3 |
R2-2204495 |
Reply LS on UE providing Location Information for NB-IoT (R3-222858; contact: Ericsson) |
RAN3 |
R2-2204509 |
Emergency services and UE rejected with "PLMN not allowed to operate in the country of the UE’s location" (C1-223045; contact: OPPO) |
CT1 |
R2-2204518 |
Reply LS on opens issues for NB-IoT and eMTC support for NTN (S2-2203064; contact: Qualcomm) |
SA2 |
R2-2206526 |
Report of [AT118-e][056][IOT NTN] RRC CR 36331 |
Huawei, HiSilicon |
R2-2206527 |
Report of [AT118-e][051][IoT NTN] Idle inactive mode |
Ericsson |
R2-2206528 |
IoT NTN idle mode corrections |
Ericsson |
R2-2206743 |
Reply LS on open issues for NB-IoT and eMTC support for NTN (R3-224007; contact: ZTE) |
RAN3 |
R2-2206769 |
Reply LS on Emergency services and UE rejected with "PLMN not allowed to operate in the country of the UE’s location" (S1-221290; contact: Apple) |
SA1 |
R2-2206840 |
IoT NTN idle mode corrections |
Ericsson |
7.2.1.2 |
CR Rapporteur Resolutions |
|
R2-2205325 |
Corrections to support of Non-Terrestrial Network in NB-IoT and eMTC |
Huawei, HiSilicon |
R2-2205326 |
Report of [Pre118-e][012][IoT-NTN] 36331 CR and rapporteur resolutions (Huawei) |
Huawei, HiSilicon |
R2-2205327 |
List of RRC Editor's Notes and proposed handling |
Huawei, HiSilicon |
R2-2205864 |
IoT NTN Stage 2 corrections |
Ericsson, Eutelsat |
R2-2206089 |
IOT NTN ASN1 RIL List |
Huawei, HiSilicon |
R2-2206629 |
IoT NTN Stage 2 Corrections |
Ericsson, Eutelsat |
R2-2206693 |
Addition of missing functionalities and corrections to support of Non-Terrestrial Network in NB-IoT and eMTC |
Huawei, HiSilicon |
R2-2206777 |
IoT NTN Stage 2 Corrections |
Ericsson, Eutelsat |
R2-2206876 |
IoT NTN Stage 2 Corrections |
Ericsson, Eutelsat |
7.2.2 |
Open Issues |
|
R2-2204593 |
Discussion on the Open issues for IoT over NTN |
Transsion Holdings |
R2-2204653 |
Beam information for the discontinuous coverage prediction |
Qualcomm Incorporated |
R2-2204655 |
Reporting remaining GNSS position validity duration |
Qualcomm Incorporated |
R2-2204710 |
[O308][O310] Discussion on the system information for discontinuous coverage in IoT-NTN |
OPPO |
R2-2204727 |
Discussion on the signaling for reporting remaining GNSS validity duration |
OPPO |
R2-2204740 |
Discussion on mac-ContentionResolutionTimer in IoT NTN |
OPPO |
R2-2204741 |
Discussion on TA report in IoT NTN |
OPPO |
R2-2204751 |
Discussion on AS-NAS interaction while the UE is out of coverage |
Spreadtrum Communications |
R2-2204752 |
Discussion on the remaining issue of GNSS Position Validity |
Spreadtrum Communications |
R2-2204753 |
Discussion on the remaining issue of enhanced spatial coverage prediction |
Spreadtrum Communications |
R2-2204965 |
Further consideration on additional satellite assistance for discontinuous coverage. |
Lenovo |
R2-2205031 |
Details on GNSS Validity duration reporting |
CMCC |
R2-2205033 |
Discussion on open issues for support of Non continuous coverage |
CMCC |
R2-2205143 |
FFS and RILZ302, H000, O302 etc for SIB32 |
ZTE Corporation, Sanechips |
R2-2205153 |
FFS on provision of remaining GNSS duration |
ZTE Corporation, Sanechips |
R2-2205238 |
[C503] Correction on ephemerisOrbitalParameters of SatelliteInfor in 36.331 |
CATT |
R2-2205373 |
Remaining issues on discontinuous coverage |
Xiaomi |
R2-2205398 |
Discussion on location report for IOT NTN |
Xiaomi |
R2-2205399 |
Discussion on the signaling of GNSS validity duration |
Xiaomi |
R2-2205400 |
FFS issues related to GNSS outdate indication |
Xiaomi |
R2-2205598 |
Assistance Information for Predicting the Discontinuous Coverage |
Google Inc. |
R2-2205600 |
On remaining issues for Location Reporting |
Nokia, Nokia Shanghai Bells |
R2-2205723 |
On discontinuous coverage and GNSS position validity |
Nokia, Nokia Shanghai Bell |
R2-2205725 |
Alignment with NR NTN for Msg3 blind retransmission |
Nokia, Nokia Shanghai Bell |
R2-2205761 |
Details of GNSS position validity report for NB-IoT |
NEC Telecom MODUS Ltd. |
R2-2205860 |
Open issues on discontinuous coverage |
Ericsson |
R2-2205862 |
Other control plane open issues |
Ericsson |
R2-2205933 |
Email Discussion Report [Post117-e][906][IoT-NTN] Non-Continuous Converge |
Mediatek India Technology Pvt. |
R2-2206115 |
ASN.1 proposal for satellite assistance information for prediction of discontinuous coverage |
GateHouse, Sateliot |
R2-2206160 |
ASN.1 proposal for satellite assistance information for prediction of discontinuous coverage |
GateHouse, Sateliot, Mediatek |
R2-2206420 |
Report of [AT118-e][048][IoT-NTN] New Issues (OPPO) – 1st round |
OPPO |
R2-2206538 |
[Offline-057][IoTNTN] Discontinuous coverage (Gatehouse) |
nnGatehouse |
R2-2206548 |
Report from [AT118-e][058][IOT NTN] GNSS Validity duration report (NEC) |
NEC (Rapporteur) |
R2-2206549 |
[Offline-057][IoTNTN] Discontinuous coverage (Gatehouse) |
nnGatehouse |
R2-2206626 |
Report from [AT118-e][058][IOT NTN] GNSS Validity duration report (NEC) |
NEC (Rapporteur) |
R2-2206627 |
Report of [AT118-e][048][IoT-NTN] New Issues (OPPO) – 2st round |
OPPO |
R2-2206794 |
Corrections for Supporting Non-Terrestrial Network in NB-IoT and eMTC |
MediaTek |
7.2.3.1 |
User Plane |
|
R2-2205161 |
Correction on sr-ProhibitTimerExt for IoT NTN |
ZTE Corporation, Sanechips |
R2-2205328 |
Correction on 36.321 |
Huawei, HiSilicon |
R2-2205724 |
36.321 corrections for IoT NTN |
Nokia, Nokia Shanghai Bell |
R2-2205959 |
TA Reporting during Random Access |
InterDigital |
R2-2205996 |
IoT NTN Uplink synchronisation and UE-eNB RTT modelling |
Ericsson |
R2-2206533 |
Report of [AT118-e][049][IoTNTN] User Plane (Interdigital) |
InterDigital, Inc. |
7.2.3.2 |
RRC |
|
R2-2204652 |
Clarification on GNSS fix |
Qualcomm Incorporated |
R2-2204654 |
RRC reestablishment between TN and NTN for NB-IoT |
Qualcomm Incorporated |
R2-2204712 |
[O300][O301][O302][O303][O304][O306][O307][O311][O312][O313] Correction on the handing of SIB31 |
OPPO |
R2-2205140 |
FFS and RILO301 etc for SIB31 |
ZTE Corporation, Sanechips |
R2-2205145 |
FFS and RILO305, X501 etc for dedicatedSIB31 |
ZTE Corporation, Sanechips |
R2-2205146 |
RILZ303 Reference to GNSS validation check |
ZTE Corporation, Sanechips |
R2-2205329 |
Adressing RRC Editor’s notes |
Huawei, HiSilicon |
R2-2205330 |
RIL H012, H013, H016, H017 : Signalling of NTN specific configuration parameters |
Huawei, HiSilicon |
R2-2205595 |
IoT-NTN System Information Validity |
Interdigital, Inc. |
R2-2205830 |
Clarification on System Information acquistion and GNSS Fix related actions for IoT-NTN |
Nokia Solutions & Networks (I) |
R2-2206529 |
Report of [AT118-e][050][IoTNTN] Miscellaneous (ZTE) |
ZTE (email discussion rapporteur) |
7.2.3.3 |
Idle Inactive mode |
|
R2-2204651 |
Clarification on TN NTN barring |
Qualcomm Incorporated |
R2-2204711 |
Correction on Measurement rules for cell re-selection in IoT-NTN |
OPPO |
R2-2205250 |
36.304 R17 editorial corrections |
Nokia, Nokia Shanghai Bell |
R2-2205331 |
Adressing 36.304 Editor’s notes |
Huawei, HiSilicon |
R2-2205861 |
IoT NTN idle mode issues |
Ericsson |
7.2.4 |
UE capabilities |
|
R2-2204650 |
NTN UE capability signaling for eMTC and NB-IoT |
Qualcomm Incorporated |
R2-2205332 |
Discussion on UE capabilities |
Huawei, HiSilicon |
R2-2205333 |
TN-NTN differentiation for NB-IoT |
Huawei, HiSilicon |
R2-2205374 |
Remaining issues on UE capability |
Xiaomi |
R2-2205594 |
IoT-NTN-only UE |
Interdigital, Inc. |
R2-2205601 |
On Capability Indication of existing IoT-Features for NTN connectivity |
Nokia, Nokia Shanghai Bells |
R2-2205863 |
On IoT NTN UE capabilities |
Ericsson |
R2-2206690 |
Introduction of additional IoT-NTN UE Capabilities |
Nokia |
R2-2206691 |
LS to SA2 on RAN2 agreements on UE capabilities for IoT-NTN |
RAN2 |
R2-2206836 |
Text Proposal for TS36.331 for IoT-NTN Capability changes |
Nokia, Nokia Shanghai Bell |
R2-2206873 |
Introduction of additional IoT-NTN UE Capabilities |
Nokia |
7.3 |
EUTRA R17 Other |
|
R2-2204467 |
LS on updates to 36.300 from LTE_terr_bcast_bands_part1 (R1-2202825; contact: Qualcomm) |
RAN1 |
7.4 |
User Plane Integrity Protection support for EPC connected architectures |
|
R2-2204490 |
Reply LS on User Plane Integrity Protection for eUTRA connected to EPC (R3-222610; contact: Qualcomm) |
RAN3 |
8.1 |
Session on LTE legacy, 71 GHz, DCCA, Multi-SIM and RAN slicing |
|
R2-2206151 |
Report from session on LTE legacy, 71 GHz, DCCA, Multi-SIM and RAN slicing |
Vice Chairman (Nokia) |
8.2 |
Session on R17 NTN and RedCap |
|
R2-2206152 |
Report from Break-Out Session on R17 NTN, RedCap and CE |
Vice Chairman (ZTE) |
8.3 |
Session on eMTC |
|
R2-2206153 |
Report eMTC breakout session |
Session chair (Ericsson) |
8.4 |
Session on R17 Small data and URLLC/IIOT |
|
R2-2206154 |
Report for Rel-17 Small data and URLLC/IIoT |
Session chair (InterDigital) |
8.5 |
Session on positioning and sidelink relay |
|
R2-2206155 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
8.6 |
Session on SON/MDT |
|
R2-2206156 |
Report from SON/MDT session |
Session chair (CMCC) |
8.7 |
Session on NB-IoT |
|
R2-2206157 |
Report NB-IoT breakout session |
Session chair (InterDigital) |
8.8 |
Session on LTE V2X and NR SL |
|
R2-2206158 |
Report from session on LTE V2X and NR SL |
Session chair (Samsung) |